Normally I hate haptic feedback, and set vibration for notification only. But today I got a Galaxy S which completely does not vibrate. Ok, I set everything that could possibly make it vibrate, but it still does not.
Is this a hardware issue or can it be fixed by any other software solution?
Please help
PS: I applied 3-button combo fix by ODIN3 method. Unfortunately, I did not pay attention to this issue before applying the fix, can this be a possible cause of the problem?
Thanks
PS: I applied 3-button combo fix by ODIN3 method. Unfortunately, I did not pay attention to this issue before applying the fix, can this be a possible cause of the problem?
Yes if the problem was not there before ..
Try a factory reset.
jje
Thanks for your reply. I did a factory reset, but the issue remains. I heard somewhere it might be caused by installing OCLF, which I also did...
I found an item name /lib/modules/vibrator.ko, guessing this is something to do with vibration and tried out but got no luck yet...
JJEgan, what's with you and not using the "quote" function? It's confusing.
what firmware are you on?
i had this weird issue on the bell i9000M on the stock 2.1 firmware (whatever the firmware version was before JH2). my text message notifications would not vibrate when i received them, but after i updated the firmware, the issue was gone.
kenrick.du said:
what firmware are you on?
i had this weird issue on the bell i9000M on the stock 2.1 firmware (whatever the firmware version was before JH2). my text message notifications would not vibrate when i received them, but after i updated the firmware, the issue was gone.
Click to expand...
Click to collapse
Mine won't vibrate at all. I am using Froyo, and have flashed a few ROMs to see if they help. No luck so far though. I am kinda thinking of sending it back to the seller
Yeah, it sounds like a hardware issue then if you're already running froyo. Hopefully they'll send you a new one that works.
Related
I just received a new Captivate from Amazon.com and it has a very annoying problem.
Frequently the home screen button or back button are activated without actually being physically touched. At times I can even watch the home screen button flicker as it is "pressed" repeatedly and the home screen is cycled through.
As you can imagine this is a very annoying problem. A Google search shows that others have had this issue as well but their only solutions have been to return the phone for an exchange. As I am unable to do that at the moment (US phone, and I am overseas temporarily), I was wondering if anyone had any success fixing this problem by using the Odin package to 'reflash' the phone. I'm going to attempt the stock Eclair installation outlined in the Development section.
Any other ideas or suggestions would be welcomed!
Had the same problem and returned it got a new one and haven't had that issue [email protected]!
After upgrading my firmware to JH3 (h t t p://forum.xda-developers.com/showthread.php?t=758176) the problem has gone away!
After upgrading my firmware to JH3 (h t t p://forum.xda-developers.com/showthread.php?t=758176) the problem has gone away!
Click to expand...
Click to collapse
Does this firmware upgrade require rooting??
Btw I was also having same problem I just performed factory reset method and boom...everything is fine since then...reset is the simple solution to most of problems..!
No it does not. But you need the version of Odin that allows you to select specific firmware and the firmware file of course. The One Click Odin won't work.
I tried that first as well but it didn't help.
glio1337 said:
After upgrading my firmware to JH3 (h t t p://forum.xda-developers.com/showthread.php?t=758176) the problem has gone away!
Click to expand...
Click to collapse
Thanks for the update on this.
I have been using some custom rom's around here, Doc's and some Darky's and they were perfectly fine.
Some days ago, I started the SGS Tools application, and got to the "Secret codes".
I was just curious about it, and I got into the "Touch key firmware version"
So there was 2 options, to upgrade the Touch key, or the touch screen.
I pressed the touch key, and then the screen said "PASS" and boom !
The touch keys stopped working.
I tried everything, wipe all, flashing back to 2.1, then back to Darky's, and Darky's Odin. Nothing is working.
It's a driver problem as it seems, can anyone, anyone please help me?
Thanks, I will be so greatful!
I came across a thread in another forum that discussed this touch key problem while I was trying to flash Darky's 9.2. You will need to flash to a stock rom. While in stock, go to your dialer and type the following:
*#*#2663#*#*
Then click Touch key FW update.
The touch keys become unresponsive if you try to update the firmware after a kernel change other than stock. Hope this helps.
Source: http://androidforums.com/galaxy-s-a...flashing-darky-v9-gt-i9000m-minimal-risk.html
xlittle_lambx said:
I came across a thread in another forum that discussed this touch key problem while I was trying to flash Darky's 9.2. You will need to flash to a stock rom. While in stock, go to your dialer and type the following:
*#*#2663#*#*
Then click Touch key FW update.
The touch keys become unresponsive if you try to update the firmware after a kernel change other than stock. Hope this helps.
Source:
Click to expand...
Click to collapse
Hey mate.
Thanks alot! but it doesnt work.
I flashed about 3 rom's. 2.1 rom, original from my country 2.2 rom,
and allways did fw update, but none working.
What can I do?!?
Did you do a complete clean install of your stock rom? What I mean by that is you wipe data/factory reset before and after you flashed your phone's stock rom. As the guide I linked utilized a carrier stock 2.2 rom, try flashing the carrier stock 2.2 for your phone. Wipe data/factory reset in recovery mode, and try the firmware update again via dialer *#*#2663#*#* and select "Touch key FW update" . Reboot your phone.
I have the Bell Mobility I9000M model, as the guide is intended for, but it should work on the international version as well (I'm assuming you are from Asia or Europe?)
Hopefully your touch key issue will get resolved, if not by me, then someone else with more expertise in this forum.
Yes, I have tried all those, but nothng helps.
Someone can help please? thx
help please?
help? please
I have exactly the same problem.##Help
help guys.. please
I have also this problem : (
Has no one any other solution for this problem ?!
Lot's here got this problem, please if someone know's how to fix the problem, please help us all. I tried all, I tried any 2.1,2.2,2.3 rom out there, the JM9 [that shouldve fixed my problem] but non helps.
I finally managed to solve the issue by reflashing to a stock 2.2.1 and using the ##code thingy.
duckbill22 said:
I finally managed to solve the issue by reflashing to a stock 2.2.1 and using the ##code thingy.
Click to expand...
Click to collapse
can you please give me the exact rom you downloaded? thanks.
I came across a thread in another forum that discussed this touch key problem while I was trying to flash Darky's 9.2. You will need to flash to a stock rom. While in stock, go to your dialer and type the following:
*#*#2663#*#*
Then click Touch key FW update.
The touch keys become unresponsive if you try to update the firmware after a kernel change other than stock. Hope this helps.
Source: http://androidforums.com/galaxy-s-al...imal-risk.html
__________________
Download Software
returnix said:
can you please give me the exact rom you downloaded? thanks.
Click to expand...
Click to collapse
The ROM in question was: I9000UGJH2
Sorry, I had to get home to look this up as I only used this ROM to solve the issue and went straight back to Darky 9.3.
I hope this helps
duckbill22 said:
The ROM in question was: I9000UGJH2
Sorry, I had to get home to look this up as I only used this ROM to solve the issue and went straight back to Darky 9.3.
I hope this helps
Click to expand...
Click to collapse
man
thanks you
so much, I really dont know how to thank you.
I will open a thread that will explain to all that this problem happend to them too.
THANKS!
Ditto, I had the same problem, bought the phone from a guy and it already had a custom firmware on it. I screwed up the menu and back keys by upgrading the touch key firmware.
I eventually found this thread, upgraded (or rather rolled back) to the original firmware (in my case I9000UGJL2) and re-applied the touch keys firmware upgrade and voila now my keys work again after a month or two of pulling hair.
nice work and lots of thanks
After a painstakingly long search (upwards of 5 hours, gee thanks SOPA) I finally got ahold of original firmware, flashed and followed the post, worked great Thx! BTW this was for a Canadian Bell GT-I9000M, which I flashed to KC1 to get to work if anybody has similar original firmware finding issues, (took a few trial and errors)
I have the same problem on my galaxy mini, anybody know a galaxy Rom that fix my problem?
Hi All,
I've been searching threads but haven't found anything much on this. I have recently upgraded my captivate to the stock Rogers 2.3.3 firmware. I've been on it for two days and so far once each day I try to wake my phone up from sleep with the power button and nothing happens. Only way to wake is to pull battery and put back. Second time it happened I called my phone and it rang but screen was just black.
Has anyone come across this? Is it this stock rom or hardware issue? It's only happened since upgrading to 2.3.3. I was on stock 2.1, 2.2 and Serendipity 7 and never had this happen before.
Any help or feedback is appreciated.
Also, I re-flashed stock 2.3.3 again this morning and it happened again.
Did you try a Wipe Data/Factory Reset ??
yes, I did both before flashing again and just this afternoon I picked up my phone and tried to wake up but no go. had to battery pull to wake it up.
?? It may be a hardware issue. I guess if you flash back to Froyo you would know for sure if it was a hardware or 2.3.3 issue...
Thats true, if it happens again I may flash back and test. Thanks
I am considering upgrading to 2.3.4 on my galaxy mini to solve the "sleep of death" problem... is anyone out there who has upgraded to 2.3.4 still having the "sleep of death" problem?
Whats sleep of death problem ?
It's when the phone is still "on" but will not wake up. The only way to get it working is to take out the battery. Many are reporting this happening every day or two.
Happens on i9000 for me, I just keep powerbutton pressed until it reboots. No need to remove battery.
I think i need to do a factory reset on phone + sd card someday, maybe it resolves it.
this happened to me too. just reset phone and when it starts, try to use the phone or just simply tap the phone every time it tries to sleep (anything works as long it doesn't sleep)... just keep on doing this for about 30min? or more
(make yourself busy while doing this cuz its gonna be boring just tapping)
I think it's related to hardware problem (not confirmed yet anyway)... Don't believe that "upgrade" could be the solution..
I actually hope so!
GT-S5570 on Train
I just upgraded today using kies.... now when I try to start up it never gets past the step where it shows the "Samsung Galaxy Mini" text. Creating another thread for this problem.
With CheckFUSDownloader (thanks to Luffarjoh - search 3D) you can download the archive used to update your fw and, so, reflash it with Odin (even more times if needed)...
GT-S5570 on the road
Doc_cheilvenerdi.org said:
I think it's related to hardware problem (not confirmed yet anyway)... Don't believe that "upgrade" could be the solution..
I actually hope so!
GT-S5570 on Train
Click to expand...
Click to collapse
Nope, it's not hardware related. Never had a SOD since I used tjstyle's CM7.
Early Gingerbread firmware from Samsung has SOD too, but I think the latest versions doesn't.
Official firmware is now on 2.3.5, FYI.
If I can't get passed the logo screen what is the best way to get my firmware information? The guides say I need this info to choose the right rom.
Thanks!
This is a Froyo problem, didn't happen in Gingerbread :3
Yeah, had the same problem when on Froyo, after flashing GB2.3.4 the problem hasn't occured.
Hello, i have my Note rooted, and installed framework for circle battery.
I have baseband XXKJ4 android 2.3.5, besides that everything is stock !
At first everything was working great, no problems whatsoever but now from time to time my soft keys freeze and i must reboot device to get them working again.
So what could be the problem? Should i unroot it and take it back to get it repaired or is that normal? How should i fix it?
Tnx for advice !
Bucika said:
Hello, i have my Note rooted, and installed framework for circle battery.
I have baseband XXKJ4 android 2.3.5, besides that everything is stock !
At first everything was working great, no problems whatsoever but now from time to time my soft keys freeze and i must reboot device to get them working again.
So what could be the problem? Should i unroot it and take it back to get it repaired or is that normal? How should i fix it?
Tnx for advice !
Click to expand...
Click to collapse
It could be the framework changes you did with the battery.
Flash a stock ROM back on it, see if that solves your problem.
Im facing same problem.. Today was the second time the soft keys wuldnt work since i bought the note 1 week ago..after i ended a phone call it took me back to the call logs so i pressed the return soft key but it wuldnt take me back to home screen!! I cant find what causes that issue however it was fixed after i rebooted the phone.. Im on stock KKA
Sent from my GT-N7000 using xda premium
Bucika said:
Hello, i have my Note rooted, and installed framework for circle battery.
I have baseband XXKJ4 android 2.3.5, besides that everything is stock !
At first everything was working great, no problems whatsoever but now from time to time my soft keys freeze and i must reboot device to get them working again.
So what could be the problem? Should i unroot it and take it back to get it repaired or is that normal? How should i fix it?
Tnx for advice !
Click to expand...
Click to collapse
That's a known issue on 2.3.5
On a number of occasions it happens after a call.
Just switch to the latest stock in the 2.3.6 series and all should be OK.
vizvin said:
That's a known issue on 2.3.5
On a number of occasions it happens after a call.
Just switch to the latest stock in the 2.3.6 series and all should be OK.
Click to expand...
Click to collapse
I also have a stock Galaxy Note & have this same problem sporadically. I don't understand your advice. Could you help an Android noob and put it in language I can understand!
Cheers
albielyons said:
I also have a stock Galaxy Note & have this same problem sporadically. I don't understand your advice. Could you help an Android noob and put it in language I can understand!
Cheers
Click to expand...
Click to collapse
He means: Just update your phone from Android 2.3.5 to 2.3.6
The forum has several threads about updating and rooting
OK, I have figured out that 2.3.6 is the android version. But my phone is already onto that version installed, so I can't upgrade to it to fix the problem....
Any other ideas?
albielyons said:
OK, I have figured out that 2.3.6 is the android version. But my phone is already onto that version installed, so I can't upgrade to it to fix the problem....
Any other ideas?
Click to expand...
Click to collapse
Try to reflash the stock rom, it might solve your proplem