Related
Bonjour
I upgraded to WM6 (pdaviet) 2 months ago (I guess..), and problems started to appear a few weeks ago. First it just was hard to boot sometimes, had to reboot several times to get it up and running, but when it could start everything was fine. Then since yesterday, it became harder. And today, couldn't start it at all. Tried several times, and everytime the screen went melted, corrupted, like if it couldn't stand an o/c, but it always runs at normal speeds. I guess it has something to do with the battery and the way WM6 handles it (or at least the implementation we have on our prophet).
I tried to hard-reset, I left it a long time on the format screen (before the actual HR) and it handled it for long enough, but the same thing started while setting up WM.... too bad !
While writing this message I tought I could try to downgrade, and I did using AKU3.3-Jester-b1.
I had no problem while the phone was in guest mode after the HR.
Everything went nice during first step upgrade, but on final reset it did the same thing, and now..... it cannot start at all !!!!
Someone has an idea ? I own a G4 and it has the following roms :
IPL 2.10, SPL 2.20, GSM 2.47 (or something like that)
It won't charge (but my batteries are full, I've got an external charger), it won't start from battery nor from power, even if the battery is removed.
Damn, at least I guess I can return it like that to orange, since it cannot start one can't see the modified rom...
If anyone has a suggestion, it is more than welcome ^^
Thanks !
Niko
huh !
back to semi-life ^^
After a few hours left alone without battery or sim card, it started again...
but it still resets every few minutes, or the screen goes melted (actually its like white scanlines that fulfill the screen).
I'll try to leave it shutdown for the night, see if I can at least put the orange splash screens and rom back for warranty purpose.
But it now has serious HW problems, for sure. And my opinion is WM6 has something to do with that. BEWARE !
Another strange thing is that I now have to keep the reset button pressed for half a second to reset, where it reseted instantly before. Those devices really have unstable hardware.
FYI, it was almost brand new, as it was warranty-replaced about one week before I installed WM6.
lastnikita said:
back to semi-life ^^
After a few hours left alone without battery or sim card, it started again...
but it still resets every few minutes, or the screen goes melted (actually its like white scanlines that fulfill the screen).
I'll try to leave it shutdown for the night, see if I can at least put the orange splash screens and rom back for warranty purpose.
But it now has serious HW problems, for sure. And my opinion is WM6 has something to do with that. BEWARE !
Another strange thing is that I now have to keep the reset button pressed for half a second to reset, where it reseted instantly before. Those devices really have unstable hardware.
FYI, it was almost brand new, as it was warranty-replaced about one week before I installed WM6.
Click to expand...
Click to collapse
Hey LastNikita,
I had the same problem ! The white scanlines thing just after re-updating a WM6 version (pdaviet), because I was tired of the constant reset issue.. suddenly, the update went wrong, and I stupidly followed the "recovery" process, which tells u to remove the battery... bang ! screen went corrupted !
Like you, I tought it was over... but I noticed that if you connect your phone and PC with USB, and keep pressed power (ON/OFF button on side) + camera after reseting (little hole on bottom - press during 5 sec!), the PC recognizes a USB device (not the usual phone drivers...) at this moment, I launched the Jester 3.3 (step1) update, in order to downgrade from the ugly WM6 pdaviet... My phone was not yet fixed (still with white scanlines), but at least, I could hear again the WM "start" sound, the scanlines would also "move" across the screen borders when I touched the screen, which made me imagine I was on the calibrating process... also, while connected to PC, after a while, ActiveSync would launch, asking for 1st time synch... this kept me confident as the phone (software) seemed to be reacting fine although HW prob...
I completely charged the phone again (till green light) then kept on reseting the phone (until I hear the WM sound) hoping the lines would finish scanning and come back with the normal .. and guess what, it did !!! Of course, PIGHEAD as I am, I wasn't totally happy it recovered with WM5, so i digged for a better rom, and I can tell you I'm very happy with the smart1 (wizard version) which works fine, but still has some minor bugs as Live Messenger not working... but runs fine (specialy when pressing the ON/OFF button !
PS: Make sure the ALWAYS completely switch off your phone (ON/OFF for 3 secs) before removing the battery... it did happen again... when I stupidly trusted the "recovery" process, again !
DUHHHH !!!!
PS: at least, now you ALL know !
Kokiri
Finally ok for warranty )))
Thanks for sharing mate
I finally managed to downgrade to my original Orange rom, and I'm in the process of putting the original Orange splash screens back (I made the nk.nbf but I can't find the right utility to upgrade... "Update utility cannot open the requested file").
BUT I still have that HW problem afterall.... so I guess it still has to go back to warranty right ? This isn't a big deal since Orange is VERY prompt (I guess I'll get it tomorrow or monday morning, the delivery guy brings a new one and goes back wiv my phone, quite nice !), and I have a button which is stucked (from the begining) anyway ^^
While I'm writing this my phone is docked and synced, and it seems fine.... but, I guess, as soon as I will reset it will start over again.... I'll keep you posted.
Anyway, I'm no longer desesperate and that's good news (for me ^^)
++
niko
yip
ok, everything's back to original.
Actually, it works well when docked, but it freezes/melted screen as soon as I tried to use it on battery, so that I'm quite sure it has something to do wiv WM6.... I'll post that on some crossbow threads this weekend if I have time enough (there are so many of them now !)....
But once more, if YOU read this, keep that in mind.
Hope you guys won't have that kind of failure while trying it.
++
niko
confused
I am having the same problem except the screen showing white scanlines everything else is working on the handset. Could it be a LCD Problem?
Me too...
I have the same issue (black/colored vertical lines and a white screen). I think it has to do with upgrading to WM6 or with overclocking with batteryStatus, not sure. This are the suspects in my opinion....
Now I downgraded to WM5 but the problem seems to persist, I disabled batteryStatus and will see if the situation improves... crossing fingers
Uhm ... possible Overclocked!
I have read 3 threads with same errors!
how much was your highes clock? do you use it for navigation? long time on highest clock or only for speed up?
i dont have a problem with scan lines but with my prophet i use the scaling option and go max to 234 i also set to 234 when using certain apps.
is this damaging to my prophet?
at the moment trying to upgrade to PDAViet 4.0.0.0.3 with a world of pain but thats another topic!
Hi all,
I read through a lot of threads and downloaded tons of ROMS for my TyTN II. Most of them were from dutty's or no thrills. Problem however is that everything seems to work, it is also very fast.
However after a while my (hardware) keyboard and also the buttons (e.g. sliding wheel and keypad on the front) does not respond anymore. When I click any of the hardware buttons the light goes on so it does react on the buttons, however it just doesn't do anything...
Did anyone else experience this issue? I will no try to switch back to the original HTC rom (6.0) since I have no choice but if anyone knows how to fix this?
P.S. I just noticed that all my buttons do not work, it is no hardware issue since It does work after a hard reset, might be caused by incompatible applications? (e.g. SPB phone or SPB theme)
Kind Regards,
Nico van der Linden
If a hard reset fixes your problem each time, then it sounds to me like a bad flash. I would try reflashing the ROM you are currently running. Make sure to hard reset immediately after the flash also.
ok thanks, I'll try to download the ROM flash again , and perform an hard reset directly after the flash. Hopefully this times the ROM update will go better.
Regards,
Nico...
Just my 0.02$:
I think this is related either to WM6.1 builds or to a hack/fix/setting that most custom ROMs use.
I flashed Dutty's Apr 01 ROM and i had this issue. Then i flashed Mobile Vista 1.3 and it happens again . So it's not present in just one ROM, or just in ROMs cooked by a certain chef.
By "issue" i mean every once in a while the touchscreen stops responding to clicks and the keys stop working (but the keys backlight comes on, so HW seems ok).
During this unusual behaviour i noticed that the device is NOT frozen - BatteryStatus updated it's CPU usage while the keys and touchscreen didn't respond, so only the input stops working, the system is ok.
I have a feeling this is a common issue, but people see it as a freeze, and think their processor is too loaded, and they don't report it.
EDIT: Oh, and i got flamed and ignored whan i reported this here: http://forum.xda-developers.com/showthread.php?t=385080
EDIT2: I have a feeling this will get a lot of attention soon, just like the time i noticed the Tytn II is underperforming, and the fact that's it's missing 3D HW support
RPG0 said:
By "issue" i mean every once in a while the touchscreen stops responding to clicks and the keys stop working (but the keys backlight comes on, so HW seems ok).
During this unusual behaviour i noticed that the device is NOT frozen - BatteryStatus updated it's CPU usage while the keys and touchscreen didn't respond, so only the input stops working, the system is ok.
I have a feeling this is a common issue, but people see it as a freeze, and think their processor is too loaded, and they don't report it.
Click to expand...
Click to collapse
The quickest way to get out of that situation is turn off the backlight and turn it back on again, aka power button...and your screen will work again.
Also I noticed that if I flash the radio again my screen taping problems go away.
Also sometimes flashing to the original shipped ROM and then flashing back to a WM6.1 ROM also works.
Well I do not have an problem with the touch screen, this always keeps working (although the device does get VERY slow sometimes) . 'Only' my hardware buttons do not work anymore (including the hardware keyboard). It is strange that it does work after a hard reset or an install of another ROM. However, also then it stops working after half a day or so.
It might occur as soon as I change the hardware button assignment but I am not sure about this yet.
However, if anyone knows a ROM where this does not occur (e.g. an original HTC WM6.0 ROM dutch or english) then please let me know which one. I just want a working Tytn II back and I do not care anymore which version .
Kind Regards,
Nico...
Ah by the way, when this problem occurs it does not go away anymore when I turn of the device. I also tried removing SIM, memory card and battery but after it is started again the problem remains. Only a hard reset solves it....
But I am a bit confused? Is there nobody else who get these issues???
yeah...
i can confirm all of your bug...
with Vega R8 italian ROM from UDK
Hi all,
I've got a strange problem with my wizard:
When I'm pressing s or h on my hardware keyboard, pocket outlook crashes and the phone becomes extremly slow - in fact, it's unusable. Amazignly this only happens, when s or h are at the beginning of the sentence (as the first letter). All other letters are fine.
The problem came up a few days ago - but I don't know what I have changed in the meantime...
Im using TNT 11.0.2.0 ROM (WM 6.1).
Any idea?
Regards,
Rudi
Is it definitely at the start of the sentence only... or could it be when you haven't pressed another key for a while, wherever you are in the sentence?
There is the feature which runs send & receive when you press and hold S. I think H is help. There are other press and hold combinations too.
It is a long shot, but maybe it is related to that feature somehow? Maybe if that feature isn't working correctly it could cause the crashing whilst it tries to load that feature. In fact the first time it runs, it asks you to confirm a message telling you how it works. If that screen got to the back somehow, maybe outlook is left waiting for your input, but you can't input OK as it is behind the current visible screen.
Of course it might be something completely different....
I tought something similar but could not find out, which function will be startet pressing s or h.
So I did a hard reset and installed everything new, and after the hard reset, s and h work as they are supposed to do. This indicates, that some software I installed (and couldn't remember what software it was) installed a function which did not work properly.
Regards,
Rudi
Hello, I have recently discovered a very annoying problem with the touchscreen on my Motorola Defy:
I have noticed that the touch screen acts strange sometimes, so I have installed a touch test application(Touchtest by Hermit). In this application I have noticed that if I touch the screen in two different points in a fast succession, a line appears between these two dots. This makes a lot of application that require multitouch pretty much useless, because I have to restart the application to have the touch screen working again.
Is there any solution for this? I have heard that this may be a software issue, so I have e-mailed Motorola, but they have not answered yet.
I have attached two pictures to illustrate what I am saying, one taken before this strange error, and one after pressing on two spots very fast. You can see the line connecting the dots in the second picture. I can make a video if you still can't figure out what I am saying.
Thank you.
Im having a very similar problem here on my defy. When I play games on psx4droid and when I keep pressing x key, it stops working for a while then I have to release the button and when I press it again, it stops working and it continues
I encounter similar problems with my Defy.
When for instance using slide to unlock , 1 / 5 sildes fails. I have to slide 2 - 3 times until it unlock.
It also scrolls very slow in applications and the same thing happens when typing a message.
Solution : Unse lock button.
It currently runs Pays ROM, but the situation appeared since I installed 2.2.1.
I don't remember having this problems on 2.1.
Don't know if the situation is only related to software but it is really annoying.
Found this info regarding touchscreen slowness, but I am using the original charger so it doesn't apply for me.
Motorola Defy Touchscreen Problem
I recently got my Motorola Defy,my Defy's touchscreen acts sometimes really weird, on keyboard it's hard to enter 'r' or 'b' and some other characters, it takes little while to unlock the phone, it automatically opens applications, I don't know if it's due to faulty handset or software, I am considering it returning to Phone4U and get a replacement handset.
What version of Android are you using ?
Same problems here, but I think it is a software issue.
I'm having the same problem on my Defy.
After a while, the multi touch stops. I posted on the Motorola Forums
https://supportforums.motorola.com/thread/44733
but no response.
I used YAMTT and when having two touches, after 20 seconds, one of them disappears
This is repeatable
2.51.1 UK with 2.1 Android
Well, it is clear that this is a problem that affects many Motorola Defy users. But I wonder if someone could fix this thing?
Looks like the new software version 2.51.1 did not fix this bug. I haven't tried it yet, but I see some of you have.
So it looks like our only solution could be a developer from XDA. Could someone help please?
This is ridiculous...i've sent my phone to motorola only because it was giving this problem and basically what i think is that their own software is causing this problem so i'll be waiting for 3 weeks and when i get my defy...it'll still have that problem...Ridiculous...
I did a bit more experimenting.
I flashed the 2.2 Finnish blur, multitouch still disappears after 20 seconds using the touch testing programs
I also booted into Safe Mode (vol up + vol down during boot)
The same problem persists; I was using gallery image zoom to test.
However, I got my friend who has a Motorola Droid to install YAMTT. The multitouch lasted about 30-40 seconds. Not sure what to make of that. He's running some version of Cyanogen Mod on Android 2.3
efpob said:
I did a bit more experimenting.
I flashed the 2.2 Finnish blur, multitouch still disappears after 20 seconds using the touch testing programs
I also booted into Safe Mode (vol up + vol down during boot)
The same problem persists; I was using gallery image zoom to test.
However, I got my friend who has a Motorola Droid to install YAMTT. The multitouch lasted about 30-40 seconds. Not sure what to make of that. He's running some version of Cyanogen Mod on Android 2.3
Click to expand...
Click to collapse
Defy doesn't support cynogen mod and 2.3
I was messing around today and even the single touch disappears after a while
30 seconds or so
Mine sometime stop response after few seconds
really wierd
Tell me who is on stock rom and is having problem..because im on 2.2 leaked..so i cant really say if u hv this problem on 2.1...
I got this response from a Motorola employee. Anyone know of a way around this?
Motorola Employee said:
If you touch the screen and don't move for a long time, the screen will eventually try to ignore that touch as it'll be considered invaild. That's what you're seeing. If you continue to move your finger(s), touch will continue to work. Also, when you release the screen, it acts to clear the invalid touch region that you generated earlier.
Click to expand...
Click to collapse
https://supportforums.motorola.com/thread/44733
have simular problems............100 procent hardware problem..... if i twist phone a little it will go back to normal for a while
any ideas for disable it?changing some parameter or something?
I have the same problem. screen sometimes go crazy. i am using stockrom eclair SEA 2.59. sometimes it seems that it tap icons or part of the screen even without I actually tap on something. and it seems it affect the capacitive button under the screen. I am not touching the search button but the search box suddenly appear.
I have to push the power button and unlock the screen to make it normal.
somebody please help us. I am also having this weird problem. Touchscreen gets pressed itself not everytime but it happens very frequently. Tried everything, hard reseted too.
At least I gotta hope that its not a hardware problem as many of u are also facing this problem. Any body please confirm if flashing cm7 has helped u or any other solution.
brjshshrma said:
somebody please help us. I am also having this weird problem. Touchscreen gets pressed itself not everytime but it happens very frequently. Tried everything, hard reseted too.
At least I gotta hope that its not a hardware problem as many of u are also facing this problem. Any body please confirm if flashing cm7 has helped u or any other solution.
Click to expand...
Click to collapse
i returned my defy months ago but what you can do is, try to flash cyanogenmod on your defy...that should fix the problem.
Hi, I've registered myself just a minute ago, reading the link that efpod left here and I've remembered that I charged my Defy with a Galaxy S i9000 charger friday (I've charged it once the batery was drained later with my original charger) and today it is failing A LOT, it's really anoying.
I got Cyanogen Mod (latest) installed on my phone so that doesn't fix the problem.
I'm uncharging it with "StabilityTest - CPU / GPU Test" and when the battery drains out I'm gonna charge it with the original one, after that, I'll test it during the day and I'll leave a messege to keep you informed.
Hi everyone, as the title says, i've been having some problems with my surface RT (from the first generation) that I bought 2 days before the Pro was released in 2013 xd
First, a while ago, a year I think, my Vol - button stop working, I don't know why, but it just doesn't work until now. *
Second, I've been realizing that the speed and the fluently have decreased, or in other words, some lag has started to appear, even if I restart the tablet. Do the ARM version of windows suffers the same problems than its x86 counterpart? I mean, that it gets slower and slower as time goes by?
And third, and the most important, for a week or two, the right edge of the screen, doesn't respond to touch, so I can't open the charms bar or press "x" to close desktop apps, unless I use a mouse. It is like an inch wide or maybe less and involves all the "height" in landscape, but when I touch that place, the screen detects it like if I'm pressing either its left or exactly at the right edge. Curiously, it is intermittent, sometimes it works fine like it should, and in others it just doesn't work. Also, sometimes it goes crazy, and that sectors act like if i'd pressing and moving my five fingers all across that area, and I have to press the lock button for make it stop.
*I didn't mention it, but my Vol + button is starting to work weird too, I have to press it several times for make it "return to life" and response.
Well, the touchscreen problem is the one that worries me the most, but due to it is intermittent... could it be related to software instead of hardware? Could it be solved?
Thanks in advance for the answers.
Regards (I always doubt if this is the correct word for the expression that goes here xd)
Edit: I forgot to mention it, but i have win 8.1
If you haven't deleted the recovery partition, you can "refresh" the tablet to restore it to a like-new-install state. That should clean up any actual decrease in speed (as opposed to mere perception of the same).
The hardware issues sound like, well, like hardware issues. You can't really do much about those except get the thing serviced; it's not very user-repairable.
I thought that using the recovery to restore it to its original state will be the option, but is anyone else getting similar issues? I was thinking that maybe the problem was an update, because I have them programmed to be installed automatically, and maybe I didn't notice it.
I guess i'll do the "refresh" after I backup my files on December for vacations if this problem doesn't disappear by itself.
This is getting weirder :S, now I can't open some modern apps, they stay forever with the loading icon in the center, this occurs for example, in the store app or In the news app, but weather or desktop (luckily) work fine.