Related
Hi,
I've been installing and testing various ROMs for my T-Mobile Leo (HD2) before and never had any problems until now. Problem is, after the last flash, I noticed the phone doesn't vibrate any more, I've checked all the settings and even turned vibrate on/off, nothing helps. Also, if I long press the end key to shutdown the phone, it freezes, I then have to press end to lock, wait about 30 seconds then unlock to be able to use again. Important to note, when the phone freezes, only the touch screen freezes, the buttons continue to work, and I can even call the last party or answer/end calls.
I flashed some older firmwares that I used to use that used to work, but these problems still persist.
Is there any way I can diagnose the phone hardware completely? Any program or tool? I live in Guyana, South America so taking it to a repair centre is not an option, basically, I have to fix it myself.
Did I post this in the wrong thread/forum? Why and I not getting any help?
I'm still having this problem and need help! Somebody... any suggestions???
Notorious_PDR said:
I'm still having this problem and need help! Somebody... any suggestions???
Click to expand...
Click to collapse
Mate, honestly, I never notice that it would vibrate on long pressing
As long as your phone is working, then you shouldnt worry about it.
Or else, you can try to restore to original stock rom and see if this is due to hardware problem or software problem
I don't mean that it vibrates on long press. I said that it has stopped vibrating AT ALL!
In addition to that, the phone freezes alot, especially when I long press the end key. It is behaving like a hardware problem, that's why I'm asking about diagnostics for the HD2.
I dont think its anything to do with the rom. I had the same problem with mine, what happens is the flash lens gets pushed inside and stops the vibrator from rotating. Just check the lens if u see it pressed, its an easy fix if u know how to take the phone apart. For instruction check out youtube. I hope this helps.
silverwind said:
Mate, honestly, I never notice that it would vibrate on long pressing
As long as your phone is working, then you shouldnt worry about it.
Or else, you can try to restore to original stock rom and see if this is due to hardware problem or software problem
Click to expand...
Click to collapse
You should probably read back my post... I said the phone stop vibrating... not that it stop vibrating on long end press... It also freezes when I long end press... Hence, the reason I asked for any diagnostics for the HD2 as I suspect it may be hardware related...
gurkhali1 said:
I dont think its anything to do with the rom. I had the same problem with mine, what happens is the flash lens gets pushed inside and stops the vibrator from rotating. Just check the lens if u see it pressed, its an easy fix if u know how to take the phone apart. For instruction check out youtube. I hope this helps.
Click to expand...
Click to collapse
This actually seems to be the problem, I will open the phone and check... Thank you so much for your suggestion, I followed this suggestion, and now the touch screen is not working... but the phone is vibrating again. Any ideas what I will have to change now?
Hello guys,
I am having this issue with my device - sometimes when I press the home button the Voice talk / command powered by Vlingo starts. I always press the button just once (I understand that it should happen when one double-presses the home button) and it is very annoying :-(
Note, that I have Settings/Motion/Double tap turned off as well. Is there any way to fix this or do you have any idea what may be wrong??
Thanks in advance!
Sent from my GT-I9100 using XDA App
while in the motion settings, you can see the tutorial clip and that double tap has nothing to do with the home button, but with double tapping the top side of the device to start voice control instead of saying "hi galaxy". so even with that switched off, your device will react to hitting the home button twice and does not really help diagnose the initial problem.
either you have a slight hardware defect in the home button, a software issue (or maybe user error). since hardware would be more severe, let's see the software side first. what exact rom do you have? device rooted or not? anything that could mess with voice input (connected bluetooth hands free, market vlingo or other tts or stt software installed...)?
also, just to exclude user error, let another person try.
P.S. are there special circumstances when this happens? like only from deep sleep, only when charging, with a connected headset, running certain apps or whatever?
Chef_Tony said:
while in the motion settings, you can see the tutorial clip and that double tap has nothing to do with the home button, but with double tapping the top side of the device to start voice control instead of saying "hi galaxy". so even with that switched off, your device will react to hitting the home button twice and does not really help diagnose the initial problem.
either you have a slight hardware defect in the home button, a software issue (or maybe user error). since hardware would be more severe, let's see the software side first. what exact rom do you have? device rooted or not? anything that could mess with voice input (connected bluetooth hands free, market vlingo or other tts or stt software installed...)?
also, just to exclude user error, let another person try.
P.S. are there special circumstances when this happens? like only from deep sleep, only when charging, with a connected headset, running certain apps or whatever?
Click to expand...
Click to collapse
Hello, thanks for your reply. I am running the device with an unmodified SW i.e. stock rom (having a branded phone from orange slovakia), no rooted just some apps installed from the android market. It is XXKE4/XWKE7, running android 2.3.3. I dont use bluetooth or handset nor dock or anything like that.
The issue seems to be completely random to me, while I usually notice it during browsing web with opera, but it happens with more apps. I don't know what is tts or stt sw, nor market vlingo. If you would like to know some more details please let me know what would be relevant for you.
I already thought about the hw issue, but I am not sure if they would accept the warranty claim as it is quite random. I thought there would be some way to completely disable voice talk as I dont expect to use it anytime in the future anyway...
As of the user error, it happens both to me as well as to my gf while using the phone for common internet use.
Sent from my GT-I9100 using XDA App
ok, that gave us something to work with. for future reference, when asking a question like this, it might speed up the process by giving as much information in the initial post as possible and let me explain why:
the fact that you use your unrooted stock rom tells me, that it is not a common and maybe reported bug that comes with a custom rom, and with an unrooted device, it is rather unlikely, that you screwed up a system component like this.
bluetooth, docks and handfrees could influence the voice input and its triggering by having their own triggers, but that is not the case.
if it happens to other people with your phone as well, it excludes your personal behaviour, tremors or whatever (no offense, you never know, just to cover everything, some people are shaky).
if it happened only in a special state, like only while sleeping for a minute or while charging, it would ensure, that it has something to do with deep sleep.
about the other things: with tts i was referring to text to speech, the engine that reads out display content, like incoming calls, text messages or navigation instructions, stt refers to speech to text, like voice input, saying hi galaxy, telling where to navigate or dictating notes...
vlingo is the engine that is used for voice talk and voice command and there is also a 3rd version, that can be downloaded on the android market, coming with yet other features and having them all present and maybe screwed up settings might have influenced anything there, however, this doesn't seem to be the case either.
so this leaves few options for how to proceed. in your place i would start off with reading this thread: http://forum.xda-developers.com/showthread.php?t=1097153
it deals with home button issues and a theory on how the home button sometimes might react as much as 15-30 minutes later than initially pressed, which might coincide with an actual press and being registered as a double press (although that's a stretch at best).
and when it comes to a next step, if you made sure, that does not apply to you, i would be uncertain, which way to go. a factory reset might help, but if, after hours of setting the device up again, you realize there has not been any change, it was nothing but work. then there are 2 things left:
either flash a newer rom using odin and any rom from here: http://forum.xda-developers.com/showthread.php?t=1075278 (full guide and download links included)
OR decide to send it in for warranty first and see what's what.
flashing a rom might solve your problems but influence your warranty state, if not done correctly and cautiously, which would make sending it in risky.
sending it in first and not getting that bug recognized or repaired for free would mean you might end up with weeks without your phone and/or a huge bill and the same issue as before.
i guess i would get a usb jig, read up on flashing, try several stock roms, not root the device and see if the bug is gone, if not, flash back to stock, make sure the flashing is not traceable and then try a local store or your carrier for a hardware replacement or repair.
Ok so I want to convey all the relevant information without this being a mile long.
I have a o2 UK SGS2 running on a 3 sim. I have flashed on Lite'ing 6.1 with ninphetmaine 2.0.5. Up until the following, everything has been 100%.
This morning I downloaded Destinia and played it for a while. Before quitting I took a quick look at in app purchases to see if they charge ridiculous prices (they do). I'm not interested so I quickly spam back to close everything. This is when **** ****s up. OS becomes unresponsive immediately and I have no choice but to pull the battery. (power menu disappears instantly, no registered actions from soft keys or menu button in OS). No change on reboot.
I try reflashing Lite'ning. Mostly no change but I got the chance to get into task manager and uninstall Destinia/Launcher Pro.
I reinstall launcher pro, and now it works most of the time except:
1. Quite frequently the voice action app will load itself, and the unlock notification will pop up.
2. MTP notification will appear occasionally and phone will act like it's plugged in
3. Random Launcher/OS crashes. Sometimes screen on but no response from apps or OS. Sometimes screen won't turn on at all, just softkeys and darkness.
4. at first unlock after boot, camera makes standard focusing sound.
5. on boot, little popup dialog will read "in app purchases not supported in this version of android".
Really I doubt there's going to be any solution other than "wipe and reflash" but I'm really interested if anyone knows what would cause all these problems.
Cheers
. I'm not interested so I quickly spam back to close everything
Whatever that means looks to be the source of your problem..
jje
JJEgan said:
. I'm not interested so I quickly spam back to close everything
Whatever that means looks to be the source of your problem..
jje
Click to expand...
Click to collapse
what this means is that pressed back from the game's in app purchases screen, back to the main menu and then back to the Launcher, I'm sure everyone has done basically this countless times.
Fine but my dictionary defines spam as a different meaning .
But as posted that's where it all went wrong for whatever reason .
jje
Right I wipe-flashed stock 2.3.5 and it's STILL doing this. Voice actions popping up at random, all sorts of apps crashing and hanging all the time.
This has to be a hardware problem now, right?
just a stab in the dark but run a virus check.
I've never had a virus in my life, but I checked anyway and nothing.
Right so I've been watching my phone today. It's still doing random voice action popups. If I leave the phone on standard standby it will be fine for a while. It will then randomly turn on the screen by itself. The screen will stay on, if i leave it long enough the whole thing become totally unresponsive. If I press power the phone will wait a few seconds, then restart. If I don't touch it, it will just restart on its own eventually.
Can anyone recommend at least, some logging software that will let me look at the underlying OS and see what's happening when this is going on.
Is there any possibility your phone also goes to car-mode by itself?
spare parts app??
Your phone is more or less doing the same thing as mine is. It's a hardware issue from the seems of it. The voice command thing is from a dirty pin in the USB connector part which apparently isn't that hard to clean, for users in the thread below it actually helped to solve the issue. But my persisting issue is the unresponsive screen and power button causing an active screen to dim out and making the screen unresponsive..
http://forum.xda-developers.com/showthread.php?t=1174291
Im getting random voice talk and mtp etc. phone is all ovr the place. flashed litening and nimphet last week and seemed fine. used mhl hdmi cable and problems seemed to start from there.
millia90 said:
Your phone is more or less doing the same thing as mine is. It's a hardware issue from the seems of it. The voice command thing is from a dirty pin in the USB connector part which apparently isn't that hard to clean, for users in the thread below it actually helped to solve the issue. But my persisting issue is the unresponsive screen and power button causing an active screen to dim out and making the screen unresponsive..
http://forum.xda-developers.com/showthread.php?t=1174291
Click to expand...
Click to collapse
Read your thread http://forum.xda-developers.com/showthread.php?t=1278790 and your problems are down to the letter the same. I've resigned myself to it being a hardware fault and put in a service request with samsung. Wish I had better news.
Yea me too. My issue is that my SGSII was manufactured in UK so I'm at odds seeing as how I'm in America. The people at the Samsung call center referred me to the UK number so I guess I will have to bits the bullet.
Tried searching around for this but hopefully someone can help.
I've got an S3 running stock 4.0.4 firmware. I'm having 2 very frustrating issues with this phone:
1) At first I thought this was a Swiftkey issue but happens with stock keyboard. when i go into the messaging app occasionally, when pressing keys on the keyboard - nothing appears. I have to quit messaging app and go back in.
2) another very annoying issue is when in the phone book and pressing the green phone button to dial someone, sometimes it will take 10 seconds for the phone to make a call. If i happen to press it more than once during that 10 seconds, it will make the call, and say for example the other person has picked it up, the dialler will then place another call - to the same person! The other person tends to say - "why are you putting me on hold and calling me again!?"
Very annoying and not sure what to do. Really do not want to do a restore.
5aq1b said:
Tried searching around for this but hopefully someone can help.
I've got an S3 running stock 4.0.4 firmware. I'm having 2 very frustrating issues with this phone:
1) At first I thought this was a Swiftkey issue but happens with stock keyboard. when i go into the messaging app occasionally, when pressing keys on the keyboard - nothing appears. I have to quit messaging app and go back in.
2) another very annoying issue is when in the phone book and pressing the green phone button to dial someone, sometimes it will take 10 seconds for the phone to make a call. If i happen to press it more than once during that 10 seconds, it will make the call, and say for example the other person has picked it up, the dialler will then place another call - to the same person! The other person tends to say - "why are you putting me on hold and calling me again!?"
Very annoying and not sure what to do. Really do not want to do a restore.
Click to expand...
Click to collapse
The least invasive solution will be to clear the cache for the all the apps affected and reboot.
Or just wipe cache from recovery and see where it goes.
sammy.sung.me.a.song said:
The least invasive solution will be to clear the cache for the all the apps affected and reboot.
Or just wipe cache from recovery and see where it goes.
Click to expand...
Click to collapse
thanks i'll give that a bash.
Was also considering just flashing CM10 jelly bean?
Flash cm10 or Sammy jb
Sent from my GT-I9300 using xda app-developers app
5aq1b said:
Tried searching around for this but hopefully someone can help.
I've got an S3 running stock 4.0.4 firmware. I'm having 2 very frustrating issues with this phone:
1) At first I thought this was a Swiftkey issue but happens with stock keyboard. when i go into the messaging app occasionally, when pressing keys on the keyboard - nothing appears. I have to quit messaging app and go back in.
2) another very annoying issue is when in the phone book and pressing the green phone button to dial someone, sometimes it will take 10 seconds for the phone to make a call. If i happen to press it more than once during that 10 seconds, it will make the call, and say for example the other person has picked it up, the dialler will then place another call - to the same person! The other person tends to say - "why are you putting me on hold and calling me again!?"
Very annoying and not sure what to do. Really do not want to do a restore.
Click to expand...
Click to collapse
Reduce animation scale to 0.5
go to setting>developer option>animation scales
You can also set no animation so that phone will response in less time
5aq1b said:
thanks i'll give that a bash.
Was also considering just flashing CM10 jelly bean?
Click to expand...
Click to collapse
How is that very different from a restore?
5aq1b said:
Tried searching around for this but hopefully someone can help.
I've got an S3 running stock 4.0.4 firmware. I'm having 2 very frustrating issues with this phone:
1) At first I thought this was a Swiftkey issue but happens with stock keyboard. when i go into the messaging app occasionally, when pressing keys on the keyboard - nothing appears. I have to quit messaging app and go back in.
2) another very annoying issue is when in the phone book and pressing the green phone button to dial someone, sometimes it will take 10 seconds for the phone to make a call. If i happen to press it more than once during that 10 seconds, it will make the call, and say for example the other person has picked it up, the dialler will then place another call - to the same person! The other person tends to say - "why are you putting me on hold and calling me again!?"
Very annoying and not sure what to do. Really do not want to do a restore.
Click to expand...
Click to collapse
Unfortunatlly mate, i think ur having problem with this stock rom did you try to factory reset your device to eliminate those bugs. or flash another Rom because this is definitly a Rom problem.
sammy.sung.me.a.song said:
How is that very different from a restore?
Click to expand...
Click to collapse
it's not lol but at least this way i'll gain as well by upgrading to jelly bean - 2 birds with 1 stone etc etc
kachrukamble said:
Reduce animation scale to 0.5
go to setting>developer option>animation scales
You can also set no animation so that phone will response in less time
Click to expand...
Click to collapse
i'll try this as well mate - thanks!
Same issues that I'm facing
I'm also facing the same issue.... Long black screen pause when exiting or moving from one app to other. Very very frustrating ....
Tried all the trick in world including those that mentioned below.... Will be returning the device and going for a iPhone 5 !
Same exact issue, any results?
5aq1b said:
Tried searching around for this but hopefully someone can help.
I've got an S3 running stock 4.0.4 firmware. I'm having 2 very frustrating issues with this phone:
1) At first I thought this was a Swiftkey issue but happens with stock keyboard. when i go into the messaging app occasionally, when pressing keys on the keyboard - nothing appears. I have to quit messaging app and go back in.
2) another very annoying issue is when in the phone book and pressing the green phone button to dial someone, sometimes it will take 10 seconds for the phone to make a call. If i happen to press it more than once during that 10 seconds, it will make the call, and say for example the other person has picked it up, the dialler will then place another call - to the same person! The other person tends to say - "why are you putting me on hold and calling me again!?"
Very annoying and not sure what to do. Really do not want to do a restore.
Click to expand...
Click to collapse
I am having the exact same issue with my S3. Sometimes calls take up to two minutes before they register. The phone remains completely responsive the whole time, and I can try to dial a bunch of different numbers (doesn't matter if I dial a number directly or if I quick dial a favorite or whatever). Suddenly, two minutes later it appears to register that, "Oh, I'm a phone!" and then dials all of the numbers all at once. Two minutes is a very long time to wait for the damn thing to dial. Especially when some iPhone user is sitting next to me going, "Seriously? You put up with that?" It is embarrassing.
I am also on the stock android 4.0.4 (verizon) and I would really really rather not have to wipe it clean and re-install.
The rest of the phone is fast (I am using go launcher) with the exception of the "Negative Colors" widget and the "Assistive light" widget. Both of those act just like the dialer. I hit the widgets and sometimes nothing happens for a minute. Again, the phone is completely responsive the whole time and I can hit these buttons over and over. Suddenly it all registers and then my screen flashes between normal and negative about a hundred times (once for each time I hit the button in frustration), and the led flash strobes on and off (again, once for each time I tried to get it to work).
This does not happen every single time though. Sometimes it behaves properly. Other times, it is super slow, but once it reacts, then I can make calls quickly until I let it sit untouched for a while. Then it gets all slow again.
I thought I'd try flushing the cache, but I cannot seem to find what cache I should flush. I can't find a dialer app, and the only other app that looks appropriate is the Dialer Storage app, but it does not have a cache I can flush.
Can anyone point me to a diagnostic tool that I can use to determine just what the phone is doing at this time? I have tried emailing myself the logs using log viewer, but they are huge and I can't seem to find anything there that I can sink my teeth into. Any help would be appreciated. My iPhone owning friends are becoming insufferable.
bvz2000 said:
I am having the exact same issue with my S3. Sometimes calls take up to two minutes before they register. The phone remains completely responsive the whole time, and I can try to dial a bunch of different numbers (doesn't matter if I dial a number directly or if I quick dial a favorite or whatever). Suddenly, two minutes later it appears to register that, "Oh, I'm a phone!" and then dials all of the numbers all at once. Two minutes is a very long time to wait for the damn thing to dial. Especially when some iPhone user is sitting next to me going, "Seriously? You put up with that?" It is embarrassing.
I am also on the stock android 4.0.4 (verizon) and I would really really rather not have to wipe it clean and re-install.
The rest of the phone is fast (I am using go launcher) with the exception of the "Negative Colors" widget and the "Assistive light" widget. Both of those act just like the dialer. I hit the widgets and sometimes nothing happens for a minute. Again, the phone is completely responsive the whole time and I can hit these buttons over and over. Suddenly it all registers and then my screen flashes between normal and negative about a hundred times (once for each time I hit the button in frustration), and the led flash strobes on and off (again, once for each time I tried to get it to work).
This does not happen every single time though. Sometimes it behaves properly. Other times, it is super slow, but once it reacts, then I can make calls quickly until I let it sit untouched for a while. Then it gets all slow again.
I thought I'd try flushing the cache, but I cannot seem to find what cache I should flush. I can't find a dialer app, and the only other app that looks appropriate is the Dialer Storage app, but it does not have a cache I can flush.
Can anyone point me to a diagnostic tool that I can use to determine just what the phone is doing at this time? I have tried emailing myself the logs using log viewer, but they are huge and I can't seem to find anything there that I can sink my teeth into. Any help would be appreciated. My iPhone owning friends are becoming insufferable.
Click to expand...
Click to collapse
have you tried a different modem( also use getril to match modem and ril)
slaphead20 said:
have you tried a different modem( also use getril to match modem and ril)
Click to expand...
Click to collapse
Thanks for the quick reply. I didn't know what a ril was and did a little research. Fascinating.
As far as I can tell, and please bear with me since I am a complete noob here (though I am resonably facile with Linux), since I am running the original ROM, I don't have any influence over the RIL. Is that correct? I downloaded getril, but it says that my device (Verizon GS3) is not supported.
What is the text that would show up in a log if I made a call? I'm going to try and search the logs again, maybe that will tell me something,
Straight to the problem: sometimes (and in a very unpredictable manner), when i have an incoming call, plenty of problems show their ugly face. First of all, i sometimes can't accept, or decline an incoming call, because the screen isn't responding to input. Sometimes i can go around this by pressing the on/off button twice, and that would enable the screen. But, sometimes even that doesn't work. The phone just keeps ringing until the caller eventually gives up. When that happens, the phone continues to function normally.
Another problem is constant vibrations i noticed in several occasions. Instead of vibrating in "pulses" or "waves", the phone just keeps vibrating constantly, which can be very annoying in combination with the problem mentioned in the first paragraph.
At first i though it's a bug in my ROM (CM9 port for legend), but have heard people experiencing the problem on other stock devices (Galaxy SII on stock ICS, for example). So it is not that rare, but to this day i haven't been able to find a solution.
Did anyone manage to solve this problem, or find any information as to how this can be avoided?
stane37 said:
Straight to the problem: sometimes (and in a very unpredictable manner), when i have an incoming call, plenty of problems show their ugly face. First of all, i sometimes can't accept, or decline an incoming call, because the screen isn't responding to input. Sometimes i can go around this by pressing the on/off button twice, and that would enable the screen. But, sometimes even that doesn't work. The phone just keeps ringing until the caller eventually gives up. When that happens, the phone continues to function normally.
Another problem is constant vibrations i noticed in several occasions. Instead of vibrating in "pulses" or "waves", the phone just keeps vibrating constantly, which can be very annoying in combination with the problem mentioned in the first paragraph.
At first i though it's a bug in my ROM (CM9 port for legend), but have heard people experiencing the problem on other stock devices (Galaxy SII on stock ICS, for example). So it is not that rare, but to this day i haven't been able to find a solution.
Did anyone manage to solve this problem, or find any information as to how this can be avoided?
Click to expand...
Click to collapse
I have the same problem with my phone. Any solution for this problem thx
Reflash, reflash, and if it happens again - reflash. The screen lock/unlock workaround was working about 90% of the time. I gave the phone to my father (clean new flash) and he didn't experience any issues with the rom so far.