Related
Hi, I am sorry if this has been posted before else where on XDA but i cant find anything on the development thread.
Is it possible for someone to make a G-Sensor calibration app that works globally for all apps on the phone?
I have the problem where if you say, use the layar app, the horizon is not level and driving games always go to the left for example.
I have rooted my phone now so cant send back for warranty. Surley a global calibration app for rooted users would be quite simple lol? not that i am a developer haha.. i have no idea, but surley its just a case of adding a number to part of the code for the g-sensor driver heh heh
Hope someone can help!
p.s Who else has this issue?
P.s. I just read on this this thread that Modaco's alpha 14 ROM contains g-sensor calibration in 'settings, sound and display and @ the bottom G sensor calibration'??
Is is possible for someone to get the bits requred to enable this on any rom that we can just flash an update.zip to get working?
sorry for putting this post in the development forum, i saw some other requests and assumed that was the place for it
so, Bump, any devs have any idea if its possible?
Bump
Calling all devs! :O) Does anyone know if its possible?
not one single person has anything to say about this? sigh...
bump from me too...
lastes cyan has issues after laying on a table.
It won't go to portrait mode.
i'll see if i can find a way to pull that little tidbit from their code. i found this while trying to find a way to unscrew my compass. i thought there was a way to calibrate it.
does anyone know where the g sensor or compass physicly is in the phone? i'm guessing in the gps box, but i dont know. in the early days of my G1, it sailed across the room a plenty due to the lightsaber/sword/fishing/gun apps. some call it Wii syndrome. i may have broken the damned thing.
Sent from my HTC Dream using the XDA mobile application powered by Tapatalk
theomajigga said:
bump from me too...
lastes cyan has issues after laying on a table.
It won't go to portrait mode.
Click to expand...
Click to collapse
Woah, I thought I was the only one with this problem.
Setting the phone on a table pretty much guarantees it going into landscape and I have to tilt it back up and forward to get it back into portrait before laying it down again.
Ok.. So I searched a while, and I'm not sure if I was just using the wrong terms, but I couldn't get a result that answered my question.
Anywho.. I'm using Fresh Toast 2.0b2, and I'm having an odd problem when playing games that have touch input.
For example... Whilst playing the game "Radiant" The phone slows down considerably when I use the touch screen to move my ship.. I would say framerates cut almost in half.. but clear up as soon as I lift my thumb from the screen..
Same thing happens in the game "Blow Up" When I tap-hold the bottom of the screen to pick up the bombs to drag to the beams, the phone slows WAAAYY down, but clears up the moment I drop the bomb/lift my finger from the screen..
Could this be a ROM problem? Background App Problem? Just one of the quirks of the Hero?
Any input will be seen as valuable.
Thanks,
~jUgGsY~
jUgGsY said:
Ok.. So I searched a while, and I'm not sure if I was just using the wrong terms, but I couldn't get a result that answered my question.
Anywho.. I'm using Fresh Toast 2.0b2, and I'm having an odd problem when playing games that have touch input.
For example... Whilst playing the game "Radiant" The phone slows down considerably when I use the touch screen to move my ship.. I would say framerates cut almost in half.. but clear up as soon as I lift my thumb from the screen..
Same thing happens in the game "Blow Up" When I tap-hold the bottom of the screen to pick up the bombs to drag to the beams, the phone slows WAAAYY down, but clears up the moment I drop the bomb/lift my finger from the screen..
Could this be a ROM problem? Background App Problem? Just one of the quirks of the Hero?
Any input will be seen as valuable.
Thanks,
~jUgGsY~
Click to expand...
Click to collapse
FreshToast is buggy right now - hence the DEV rom titleing.
I also have noticed general touch bugyness. Especially slow responses to touch.
Kcarpenter said:
FreshToast is buggy right now - hence the DEV rom titleing.
I also have noticed general touch bugyness. Especially slow responses to touch.
Click to expand...
Click to collapse
So should it be considered an actual BUG for FT?
jUgGsY said:
Could this be a ROM problem? Background App Problem? Just one of the quirks of the Hero?
Any input will be seen as valuable.
Thanks,
~jUgGsY~
Click to expand...
Click to collapse
Not a ROM problem, Not specific to your device. I feel like its a problem with HTC's multitouch drivers.. Ive noticed the same problem since I got the phone in October. I'm pretty certain when you touch the phone, the Hero is looking for another touch point so it delays the phone.. The HTC Hero doesn't use the same multitouch drivers as other 2.1 devices even on the 2.1 ROMs, Thats why most multitouch programs on the market dont work right for the Hero, and also why I'm jumping to EVO, Hopefully HTC EVO doesn't have the same problem.
mental26 said:
Not a ROM problem, Not specific to your device. I feel like its a problem with HTC's multitouch drivers.. Ive noticed the same problem since I got the phone in October. I'm pretty certain when you touch the phone, the Hero is looking for another touch point so it delays the phone.. The HTC Hero doesn't use the same multitouch drivers as other 2.1 devices even on the 2.1 ROMs, Thats why most multitouch programs on the market dont work right for the Hero, and also why I'm jumping to EVO, Hopefully HTC EVO doesn't have the same problem.
Click to expand...
Click to collapse
That definitely makes sense. Wish I would've known about the EVO previous to my purchase of the Hero..
So I did 2 neocores. One without touching the screen got me 25 dos. Then I touched the screen thru the whole benchmark and got 4.9 dos. Wow that's a big difference!
-------------------------------------
Sent via the XDA Tapatalk App
Kcarpenter said:
So I did 2 neocores. One without touching the screen got me 25 dos. Then I touched the screen thru the whole benchmark and got 4.9 dos. Wow that's a big difference!
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
That should be seen as a deal breaking bug for the Hero.. We should all go to Sprint and DEMAND EVOs.
Unless its not present in the official 2.1, I'm going to do what I can to get an EVO.
yeh its really weird how it works right. .27 and touch input didnt play well. at all. the biggest problem is the sh*t digitizer we have. it only senses x OR y moving AWAY OR TOWARDS eachother. it isnt true multtouch. a good example is to download multitouch paint from the demo market. it will read both fingers fine until one crosses the x or y axis in opposite directions.
but anyways back to when you touch, i think toasts source is amazing for the .29 but once htc releases the real .29 source he will really work his magic. .29 fixed alottt of the issues with stuff like music and touch having their own "processes". in .27 they were all bunched together and that made ultra lags while using bt and messing with phone.
This is fixed in Fresh Toast 2.1Final.
I love those two guys.
Hey guys,
Just to let you know there is an application out there now to take care of force recalibration of the screen.
When I first got my nook I know it didn't register touch properly, so I ran some commands and it started working fine.
Decided I should make my first app something that helps people, so here you go. Checkout "nook screen recalibrate". It's a simple minimalistic application the re calibrates then reboots
Updated Version 2.0
* Better GUI
* Button to start process
* Lowered MinSDK to support froyo (untested)
Here's the market link.
Helpful since you don't have enough posts to post links yet. But thanks for this app!
Ironically when I go to the link and try to push it to my NC, it says it's not compatible. :X
Fine print mentions that is only works with GB (android 2.3 and above).
yep.. i dont think any rom uses anything lower than that
is it different from this app:
http://forum.xda-developers.com/showthread.php?t=934500
assid2 said:
yep.. i dont think any rom uses anything lower than that
Click to expand...
Click to collapse
The nookie froyo is based on 2.2.
If your software doesn't require 2.3 functionality, can you lower the required API to '7', which is the stock Android API level (2.2/Froyo)?
nolook said:
is it different from this app:
http://forum.xda-developers.com/showthread.php?t=934500
Click to expand...
Click to collapse
Not sure what exactly that application does.so can't comment.
Sent from my Nexus One
byronczimmer said:
The nookie froyo is based on 2.2.
If your software doesn't require 2.3 functionality, can you lower the required API to '7', which is the stock Android API level (2.2/Froyo)?
Click to expand...
Click to collapse
I think it should work. I shall reduce the requirements.
However there is no way to check cause my touch is working perfect now
However I find it performs better slightly if I do this once a week
Sent from my Nexus One
Updated release v2.0
Updated to version 2.0
* Better GUI
* Button to start process
* Lowered MinSDK to support froyo (untested)
Force closes on nookie 2.2
cowballz69 said:
Force closes on nookie 2.2
Click to expand...
Click to collapse
Strange, I had reduced the minimum requirements
I have no other froyo device to test on, let me check once again against an emulator
Sent from my Nexus One
Ok maybe this is in my head, but if I run this every couple nightlies, touch feels slightly better and responsive.
Maybe it's the nightly, maybe the way it interacts, maybe the screen de sensitises over time, maybe it's all in my head
If anyone cares to do some testing, that would be great
Sent from my Nexus One
cowballz69 said:
Force closes on nookie 2.2
Click to expand...
Click to collapse
Let me know if you wanna try this so I can publish to the market
Sent from my NookColor using Tapatalk
This may sound crazy but after running this I think that the screen is actually leases responsive and now shows the "ghost" touches so badly that the on screen keyboard isn't usable. Is there something to do to fix this?
Try cleaning your screen prior to running the application, make sure you don't touch the screen prior to restarting
Sent from my Nexus One using Tapatalk
kruuth said:
This may sound crazy but after running this I think that the screen is actually leases responsive and now shows the "ghost" touches so badly that the on screen keyboard isn't usable. Is there something to do to fix this?
Click to expand...
Click to collapse
same thing on my end. I ended up reflashing the latest cm7 nightly and its back to the way it was
Sent from my NookColor using Tapatalk
That's extremely strange. First time I've heard issues like this crop up. Do you have a screen guard or something
Sent from my NookColor using Tapatalk
For those who would want to try, scews the S2.
But the link from nolook actually fixes it.
nolook said:
is it different from this app:
http://forum.xda-developers.com/showthread.php?t=934500
Click to expand...
Click to collapse
edit: only fixed it for a short time. i'm back with some bad touch.
can you attach the .apk i cant go to market to download!! plsss
Hey folks,
I'm experiencing with my IS, as mentioned in the title, an input lag of the touchscreen. It is not really disturbing, but the fact, that my friends Wildfire recognizes the input better, with Stock 2.1 ROM installed, bothers me really
In the moment I'm S-off on Android Revolution HD 1.1.2, which has a slightly better input than stock 2.3.3, but it is still there. Please tell me, if you are experiencing similar problems.
thanks Max
Only thing I've noticed so far is that if you drag slowly In some applications (like the browser, doesn't matter which browser I'm using) it doesn't scroll at all... but in the settings menu I can swipe downwards as slow as I want to, so I guess what I'm experiencing is software related...
What I really want to know is if I'm alone, or if there has noticed the same thing
Sent from a dumb phone
with my IcS... ive noticed that certain parts of my screen at the randomest times will stop recognizing input.... for me this happens exactly at the O and N key... after leaving it for a few seconds... it starts working again so not much of an issue to me...
there is an app in market place called touchscreen booster... maybe apply that and see if that helps u change the sensitivity...
danial.aw said:
with my IcS... ive noticed that certain parts of my screen at the randomest times will stop recognizing input.... for me this happens exactly at the O and N key... after leaving it for a few seconds... it starts working again so not much of an issue to me...
there is an app in market place called touchscreen booster... maybe apply that and see if that helps u change the sensitivity...
Click to expand...
Click to collapse
thanks for the advice danial.aw. I tried your method, but the only touchscreen booster app i found in the market was for SGS, so that hadn't had any effect
Keeps annoying me buying a 500$ phone that has such a crappy touchscreen...
Sounds to me like you might have a faulty unit if it's bad with both stock and custom ROMs. Never had any issue with mine.
doctorsax said:
Sounds to me like you might have a faulty unit if it's bad with both stock and custom ROMs. Never had any issue with mine.
Click to expand...
Click to collapse
any chance I get warranty for that? the lag is really minimal
Infinite104 said:
any chance I get warranty for that? the lag is really minimal
Click to expand...
Click to collapse
Not a clue I'm afraid. Always worth asking them I suppose.
well yes it says thats its for SGS only... but the app worked on my Atrix when i had it... so im assuming it might actually help more phones than that... try it out and see...
Doesn't make any difference no matter what i set in the app. I will drive to a store today to see if it might be subjective but I don't think so.
Edit: well it's not only subjective, I'll give the warranty a try, lets see how the will react
wooh got all of my money back, I'm moving to WP7 now. Android hasnt persuaded me...maybe again when 4.0 comes out.
Infinite104 said:
wooh got all of my money back, I'm moving to WP7 now. Android hasnt persuaded me...maybe again when 4.0 comes out.
Click to expand...
Click to collapse
If you are leaving android id probably recommend waiting for the next iPhone not wp7
Sent from my HTC Incredible S using XDA App
God WP7 is woeful, the mango update had better fix/add a lot of features...
No I've tested the one from my sister for already two months and I'm very content with WP7. A Phone should be fast and I'm not really into Apple's politics.
You will be in microsofts politics though. WP7 is as closed down as ios. At least with apple you get a good warranty service.
Sent from my HTC Incredible S using XDA App
Sometimes when I'm tapping certain icons at certain times I will have to tap twice becuase the first time it didn't recognize my tap. Sometimes even multiple times. But other times my phone will run as smooth as butter. Hardware or software issue?
Same issues ...
I have the same issues.
This issue occurs often after I unlock my Phone and also during use.
In my opinion that's not acceptable!
How did you act?
Did you send it in?
Pet hate: "Smooth as butter" ARGGHHHHHHHHHHHHH!!!!!!!!!!!!
And relax.
Yes, sometimes it doesn't recognise it. Even sometimes it will actually highlight the icon, so it's recognised I've pressed, but then done nothing with the action.
I would say software issue.
cspius said:
I have the same issues.
This issue occurs often after I unlock my Phone and also during use.
In my opinion that's not acceptable!
How did you act?
Did you send it in?
Click to expand...
Click to collapse
I returned my phone because it was driving me insane.. but yes it's probably a software issue. I bought a Nexus S from google, and it's better, but sometimes it still happens on my NS, however much less often then on my O2X. But i would say just try using a different kernel or rom. CM7 still had the touchscreen issue. So that's why I kind of gave up on this phone.
Scougar said:
Pet hate: "Smooth as butter" ARGGHHHHHHHHHHHHH!!!!!!!!!!!!
And relax.
Yes, sometimes it doesn't recognise it. Even sometimes it will actually highlight the icon, so it's recognised I've pressed, but then done nothing with the action.
I would say software issue.
Click to expand...
Click to collapse
hahaha yeah sorry I don't know why I included the "smooth as butter" cliché. I didn' want to but somehow it just popped into my head. And I'm as relaxed as relaxed can get
I have noticed that o2x screen is not that sensitive. For example in "where is my water " it was difficult to draw lines as precise as on an iphone or gs2. Maybe my fingers are faulty
buluba89 said:
I have noticed that o2x screen is not that sensitive. For example in "where is my water " it was difficult to draw lines as precise as on an iphone or gs2. Maybe my fingers are faulty
Click to expand...
Click to collapse
I agree. I now have a nexus s therefore i think that Samsung>LG.
From the moment I installed RC's ics cm9 I never had touchscreen issues again. On the contrary, now I find the screen too sensitive.
nuvo84 said:
From the moment I installed RC's ics cm9 I never had touchscreen issues again. On the contrary, now I find the screen too sensitive.
Click to expand...
Click to collapse
Screen sensitivity has been fixed in the latest kangs.
Sent from my LG-P990 using xda premium
hisham027 said:
Screen sensitivity has been fixed in the latest kangs.
Sent from my LG-P990 using xda premium
Click to expand...
Click to collapse
I know.
That's funny... I'm still running stock 2.2 on my O2X and I had no trouble triple ducking all levels in where's my water... Now I'm cutting ropes
Hi, i personally dont think this is a problem with our touch screens, i have it happen to me when unlocking the phone etc, but i think its because we try to tap an icon to quickly before we give the phone chance to fully unlock, i've noticed if i wait just a second or 2 after unlocking it doesnt happen, i think its lack of ram in the o2x, it not quite fast enough for our speedy fingers, lol.
---------- Post added at 05:06 PM ---------- Previous post was at 04:43 PM ----------
wayneace8888 said:
Hi, i personally dont think this is a problem with our touch screens, i have it happen to me when unlocking the phone etc, but i think its because we try to tap an icon to quickly before we give the phone chance to fully unlock, i've noticed if i wait just a second or 2 after unlocking it doesnt happen, i think its lack of ram in the o2x, it not quite fast enough for our speedy fingers, lol.
Click to expand...
Click to collapse
Also i forgot to mention, if i turn off all animations this also decreases the chance of this happening.