Okay, now here's something related to hardware development for all you hardware tweakers
I know it's a noob question, but there hasn't (yet) been a post like this (until now).
Is it possible to take your Bravo apart and take another screen (with the same size and thickness, of course) and replace them?
I'm asking because I can't even play Slenderman on my phone, because of the buggy touchscreen (that only supports two points, and even those two glitch out!).
So, if I found a screen with the exact size and shape of my Bravo's and then replace it, would that work?
Thanks
First, desire supports only dual touch not multitouch.
When you say screen what do you mean, an LCD or touch screen (digitiser)?
Umm... I though a screen is just one block...
So, you're saying that there are two different parts I can buy...? And if I understand, one is the display, and the other is the thingy that detects touch input...?
Well, I'm just asking if there's a way to improve the touchscreen, because there's SO MUCH LAG and glitching! And since software can't fix that, I thought changing the hardware would help...
But since (obviously, as you say) the Desire only supports two touches (both from the software and the hardware part), there is no fix?
P.S.
Dude, how come you've ALWAYS got an answer for me? O.O You're like a freakin genius!
I'm Serbian...
For me my touchscreen works just fine, and most depends on which rom you use. I have Galaxy Tab 2 and I have to say that I'm more satisfied with screen calibration and usage on Desire.
Well then, which ROM makes the screen work best...?
Because on every single ROM, there's a glitch when I press on the screen with two fingers (in opposite corners) and then, if I swipe both fingers over either axis of the screen, there's a serious glitch, where my 1st finger controls the x coordinates of the second touch (and vice versa) and each finger controls the y coordinates of its' touch...
(if you understand any of that)
If I compare my Desire's screen to my friend's Samsung Galaxy S Plus, there's a BIG difference, one of the biggest are the ones where his doesn't glitch over an axis, and the other one being his screen supporting (at least) 5 fingers.
So, if the best solution is the ROM, what do you (oh, Great one) recommend?
I've tried MIUI, various stock versions, CM7, ICS (NikezLente and SpazeDog), and I'm currently on MildWild 4.3 final (based on Oxygen)... And all have the same issue...
I think you're asking too much...
So I'm either stuck with glitches or I buy a new phone (or go back to my (almost) broken Nokia)...
Or, I steal my friend's phone while we're on the bus and play slender there!
Mission accomplished
Related
My defy has a problem in the touchscreen on the left most side, I almost cannot type q or a (Tried Touch Test app and it shows the same, the touch doesn't extend to the left most side of the screen).
Besides, in so many times it just freezes until I turn the screen off and on again (and wait for the next freeze).
Checked on the forum, seems only one person other than me having the 2nd problem and none got the first.
Anyone can advise on a solution before I will take it to the service center?
Thanks.
Max
Protective case may cause the problem.
My defy is 'naked'...
The problem exists before I have the protection screen, it didn't go worse (or better).
Do you have any news?
Was it hardware related?
I was playing with my GF's Nook the other day and thinking about what a nice size it is for e-Reading. Now, I realize it has a higher screen resolution that WP7 doesn't support, so I wasn't thinking of going that far.
But I did get to thinking: is there a 7", 800x480 capacitive screen on the market that could be made to simply "plug in" via the same type of connector as the focus uses, and just work? In that case it wouldn't be *too* difficult to transplant the rest of the focus' guts into a bigger chassis (maybe adding a bigger battery since the extra space would be there anyway). Anybody thought about this or have some idea what one would look for?
Thanks!
So I'm guessing nobody has any idea or interest in exploring said idea?
The chances of that working are pretty darn slim. I'm not really into the hardwaret thingy, but I'm pretty sure you would need to know what interface to the display is used on both devices. They need to be the same, or you'll need to find a way to convert the signals, which means a lot of work and room for error I guess.
I would say it's possible, if you find a device with the right resolution and display interface/controller.
The display itself should work, since a display is just a display... It only receives data what to display. But dunno if the touchscreen would work out of the box, maybe different systems use different protocols in sending/receiving/processing data from the touch panel... But then again, I don't have my diploma yet
The displays must have the same controller. Or using the controller from the Focus - but don't forget, that it is AMOLED, so it might work totally different.
I don't think it is possible without too much effort. You should get some x86 tablet and run WP7 emulator on it . Or make an app for the W7 that looks like WP7.
Basically you would need to have two drivers, or make the other side compatible with existing drivers.
The screen and the touch panel.
I don't know what type of touch panel you have, but WP7 uses capacitive screens, this is a big requirement because you won't work around it easily.
The way the positioning data is transfered matters allot, because this can kill the accuracy at the least.
Next, the screen needs to know how to display the data received from your device, I assume the connector won't fit out of the box so thats the first challenge. Then you need to make sure it's receiving the correct data over the correct lines. It is not the same as plugging in a D-SUB/DVI cable.
So, if you have knowledge of some hardware modifications (electro) then you will stand a chance, otherwise you'll probably end up wasting two devices.
If you can spare both, I would say go for it. Otherwise I would think twice if I were you.
Yeah, I'm way too lazy (well, too busy with school) for all that . I was just randomly thinking about it the other day, how nice it'd be to have WP7 on a decent sized screen for an ereader, given that the Kindle app works great on the device. I guess I was hoping that there might exist, essentially, an "embiggened" version of the exact same screen, with the same connector, to simply be driven off the Focus' existing controller and hardware. Capacitive, obviously--WP7 on Resistive would lick all kinds of donkey balls, I'm sure.
My Desire Z had a fall, and has developed two problems
1 - The hardware keypad has started to take hard-press and sometimes prints double characters on single press. I think the alignment is out or something... any other guess ?
2 - The touch screen sometimes stops working from an inch up from the bottom and continues to half an inch. Before and after that patch, the touch always works fine . Mostly, the whole touch screen works fine. But when the patch gets non-responsive, I have observed that by turning the screen off and on a couple of times makes it work again. I am not very sure what the problem is. Any clues ?
Thanks
I'm also experiencing a similar issue - for me it's usually an area that corresponds to the top row of the
on-screen keypad (for unlocking) or the top of the area for unlock patterns (portrait orientation).
Mine is a 2 year old DZ w. Cyanogenmod 7.1
No HW key problems & no droppage.
Liberal application of isopropyl alcohol and a microfiber cloth - especially around the edges of the screen
seem to help a little bit but not often enough to be better than random.
Switching the screen off and on occasionally helps but most often I get annoyed and use the HW keys to
unlock.
I have noticed that, after powering on the device, the SIM-lock keypad works just fine but the (different)
screen-unlock keypad fails. This leads me to believe it to be a software issue.
/b
I have had this experience on my G2
No fix for me but his my experience check out the url!
http://forum.xda-developers.com/showthread.php?p=31264095
Sent from my HTC Vision using xda premium
Thread moved to Q & A section.
So i am going for Digitizer replacement will post the result when the phone is back.
And what about the Keypad taking hardpresses ? what can be the issue there ?
so my desire z is in the shop for repairs. lets see what problem is diagnosed.
I have read in another thread in this forum that the hardware keyboard (need to press hard on some buttons) issue can happen when the phone falls.
Apparently, the flat cable that connects the keyboard to the rest of the phone gets loose and causes such trouble.
Since your phone is in for repair, I'm sure this will get sorted when U get it back.
ok so my phone got back from repairs, the guy couldnt fix the touch-screen rather made it worse. Now the touchscreen doesnt work at all. So i cant unlock the phone and cannot test the Keyboard problem. The guy said the touch problem is related to the ribbon cable and not the touchscreen itself.
Note 1: He says he tried replacing the touch panel altogether but it didnt work.
Note 2: I still think the ribbon is fine (call it intuition)
Note 3: I am giving my phone for repairs again, but this time to HTC service center which would probably cost me a lot more than third-party repairs but at least it will get fixed.
I will update when I my phone back from HTC service center.
Could you not unlock the phone by opening the keyboard ?
It does smell to be an issue with flat (ribbon) cable to me as well. As if there was some loose contact before (caused by you dropping it), and after the repair guy took the phone apart, he probably made even bigger mess by ruining the flat cable completely.
From my experience (and I've claimed warranty 3x for the broken digitizer (touch panel)), if it's broken, an area of the screen (or the whole screen) will be permanently dead. It would not come back to life every now and then.
btw, mine always started being unresponsive in the very middle of the screen, a bar of height around 1 cm (somewhat less than 1/2 inch). Each time they replaced the digitizer.
If it;s the flat cable, you shouldn't end up being charged too much - those thingies are very cheap (in China) and the labour will probably be the majority of the price. Fingers crossed.
So I got my phone back again... The HTC repair center was not located in my city so I went to another (better known) repair shop. The guy said, "your phone hasnt been opened at all from the touchscreen side, any *repair guy* who claims he has opened it and tried this and that but couldnt fix is simply lying. This said, he opened up my desire z replaced its Touch Panel and voilah! my desire z is sensing again in 15 mins
What's the status for the keypad and need to press it hard to work ?
nope... I had it cleaned using alcohol / thinner. now it works fine.
So, I updated to CM 7.2 last night but the touchscreen problems are still there.
Updated using CWM and deleted data & cache whilst doing so.
I really hate the prospect of getting a new phone as the current models available
in DK are all without physical keyboards
Its been some days, I'm experiencing this weird touch screen problem.
My DZ touch screen doesn't respond properly.
For example:
If i see an image and slide just one finger up and down then it would zoom in and out. And then the whole screen becomes unresponsive.
It seems as if, its touched by itself. Even the softkeys would go numb. Only the haptic feedback of my search button works at that moment.
But the trackpad works perfectly.
But, If i lock and unlock the screen using power buttons, it would work properly for some few moment and then again the problem repeats.
At present I'm repeating this process of locking and unlocking screen to use my phone.
One even worst weird thing is that, if the device is connected to a charger and kept on the table or floor. This problem doesn't occur.
I have done system format, restored my nandroids and even changed Roms. The problem still exists.
Please note, i don't use any Casing or covers that would press the device hard for malfunctioning of screen. I have even removed and replaced my screen guard.
I'm sure, its not a software issue.
And even i dont think its a strip issue, because i dont use my physical keyboard always.
Can anyone say what hardware issue it might be..?
Or what i need to do? I'm really out of options.
Do i have to replace my whole screen or the digitizer..?
Thanks...
Thats no fun,
As you stated it's more than likely a hardware fault, the two most likely culprits would be the digitizer or the main flex cable
Which would be this and this
both relatively easy to replace depending on your experience
in 4.x and up ROMs check the developers setting to show touch or use apps like
z device test
or
yet another multitouch test
these wont help you fix the issue but may show you where the bad points are on the screen
best of luck
I know the problematic spot. Its near Search softkey. Even Yet another multi-touch test would stuck at that spot....
As you can see in the image, that i'm not holding anywhere, still it shows that somewhere around Search softkey its touched by itself.
In second image, If i move my fingers around, it would show the other touch responds, but if i slide near search, it would go and stuck there itself.
So, i guess i would first go with the flex cable.
In actuality I'm leaning toward the digitizer in your case, but its possible to be either.
And if you have a spare phone it may be worth disassembling even without buying anything. On a G1 I once fixed a similar issue just taking out the digitizer and cleaning the contacts on the ribbon and the edges of it as well, when I put it back it worked like new. I think some dust may have gotten into the edges but it may be worth a shot before buying anything... But could make matters worse so if you don't have a spare, buy parts first
Best of luck
Sent from my Nexus 7 using XDA Premium 4 mobile app
I guess i should try disassembling and clean it first. If it still persists then i would go for digitizer.
And thanks for giving a hope.
Thanks...
Hi All!
I just got a new a70 5 days ago, it's performing very well, but i did notice one thing. Sometimes my quick touches when i just very quickly and barely touch the screen, the touch is not registered. I activated the factory diagnostic mode (*#0*#) and tested and got some interesting results. If i touch the screen quickly enough, the touch is not registered at all, even though i apply a substantial force. I can do this like 3-4 times out of 10 if i really try. I also tried it on my galaxy S5, and although I could reproduce the same issue, it was much harder to get it to miss a touch than on my brand new a70. I did try it with and without a screen protector and it didn't make any difference. I'm actually surprised, I didn't think I can touch the screen too quickly so that the sensor (or software?) fails to register it. My question is: is this an expected behaviour, or something that should be looked into? It doesn't really affect everyday use, but ever since i discovered this I'm now always having this weir feeling anytime i'm about to touch the screen that "is this touch going to miss?". So my questions are the following:
1. Is this behaviour normal?
2. Why does my S5 seems to be more "reliable" and is harder to get to miss a touch.
3. Is there a 'minimum touch duration' for these capacitive screens?
4. Anybody else who has A70 experienced this, could try it out?
(it was not very easy to reproduce at first. i started noticing it when i wanted to open messenger chats, that some of my touches missed. for the issue to be easily reproduced one would have to try and tap as quickly as possible, so that your finger touches the screen for the shortest time possible)
crazylachesis said:
Hi All!
I just got a new a70 5 days ago, it's performing very well, but i did notice one thing. Sometimes my quick touches when i just very quickly and barely touch the screen, the touch is not registered. I activated the factory diagnostic mode (*#0*#) and tested and got some interesting results. If i touch the screen quickly enough, the touch is not registered at all, even though i apply a substantial force. I can do this like 3-4 times out of 10 if i really try. I also tried it on my galaxy S5, and although I could reproduce the same issue, it was much harder to get it to miss a touch than on my brand new a70. I did try it with and without a screen protector and it didn't make any difference. I'm actually surprised, I didn't think I can touch the screen too quickly so that the sensor (or software?) fails to register it. My question is: is this an expected behaviour, or something that should be looked into? It doesn't really affect everyday use, but ever since i discovered this I'm now always having this weir feeling anytime i'm about to touch the screen that "is this touch going to miss?". So my questions are the following:
1. Is this behaviour normal?
2. Why does my S5 seems to be more "reliable" and is harder to get to miss a touch.
3. Is there a 'minimum touch duration' for these capacitive screens?
4. Anybody else who has A70 experienced this, could try it out?
(it was not very easy to reproduce at first. i started noticing it when i wanted to open messenger chats, that some of my touches missed. for the issue to be easily reproduced one would have to try and tap as quickly as possible, so that your finger touches the screen for the shortest time possible)
Click to expand...
Click to collapse
Yeah the touch on this device is horrible. Don't listen to fanboys, this device has a couple of issues other than the touch screen having an awful response time.
Check:
+
The SD675 isn't well optimized for most games, so it lags in most of them, while on the A50's weaker processor, the Exynos 9610, games work just fine. Most of the time, they work better on the A50 than on the A70.
And there's another issue with dark colors being turned off instead of dimmed, because the screen doesn't know the difference between "dark" and "totally black". I'm gonna demonstrate this later by comparing the A70 and A50 side by side.
The A70 has a stronger CPU than the A50. The A50 has a stronger GPU than the A70. The A70 has better battery life.
That said, yeah touch problems. I notice it all the time when browsing. Trying to tap on small links are not registered most of the time. I have to zoom in.
I believe it to be a hardware issue that is not fixable in software.