Related
Hello all.
I did do some searching before this post, but I was unable to find anything on it. So if the answer is already online some where, I apologize.
My Samsung Vibrant recently stopped auto rotating. I checked to see if my son had accidentally unchecked the option, and it was okay. I've tried unchecking, rechecking, battery pulls, clearing cache, and nothing worked.
I then backed up all my stuff, then did a factory reset. After rebooting, it worked. I restored from the backup and it was broken again.
I then went into the settings and looked at the horizontal calibration. When the screen with the little blue ball loads, the ball doesn't move as I tilt the device. So again, I did a factory reset and went back to the settings. This time the ball moved.
I'm not an android developer but I have some programming knowledge. From what I've seen, I conclude that the accelerometer is not broken, and that for some reason, something in the software is now preventing the accelerometer from being registered
My ROM is Trigger3.2-final, Froyo 2.2, KB5, voodoo lagfix, and I've been using this for a long time. So that makes me think that it was part of an app update that I've done recently. The bad part about that is I was slacking on my updates and the last time I updated, I updated 23 apps.
So, before I go through the process of uninstalling apps one by one to see if one of them is causing the conflict, I'd like to find out if anyone else is seeing this issue, and if there is any solution.
Let me know if you have any questions our need more info about the phone.
Thanks!
Reg.
Sent from my Galaxy Tab
I have the same problem. Running Bionix v1.3.1. Did you ever figure out what the problem was?
believe this or not I had the same problem. Once flashing any rom from stock I would get stuck in landscape mode. The problem ended up being a dirty usb port. It was "shorting" pins and thought it was plugged into a dock. Cleaned the usb port and it worked fine again.
My SGS2 stopped vibrating. Tried flashing, un-rooting, restoring stock and factory settings. None of these worked.
I am inclined to think that it is a hardware problem.
Has anyone else been dealing with issue? I read some posts on XDA regarding this matter but they were software related as opposed to hardware. Can anyone post instructions on how to fix it or provide any solutions for this issue?
If its hardware, why not flash stock, remove binary flash count with USB jig, and return for warranty?
Sent from my GT-I9100 using xda
premium
UpInTheAir said:
If its hardware, why not flash stock, remove binary flash count with USB jig, and return for warranty?
Sent from my GT-I9100 using xda
premium
Click to expand...
Click to collapse
Cannot get jig in Palestine. Bought the phone from the UK. Sending it back will be problematic. I will look for a repair shop.
Thanks for the quick reply
That's a "bummer" (bad luck). You could make a jig, but as you said that it would be problematic to return. Hope you can sort it easily. Sorry, can't think of anything of use right now.
Sent from my GT-I9100 using xda premium
hey there,
i got the same problem. no more vibrating at all. not with calls or notifications and not as haptic feedback. it started today (was still working in the morning), though i did not drop the phone or anything.
i am still hoping too find that it's a sw-problem. but all potential solutions i find do not help. so i guess i have to contact samsung.
but before i do that i have to get rid of all "hacking".
could you plz tell me what i have to do?
i have now cm9 20120402 nightly.
but i still have a cwm-recovery-backup of the original touchwiz (gingerbread).
-so first i make a backup of my current rom via cwm and of all my apps via titanium and store everything on my pc.
-i flash my touchwiz-backup
-i get one of those: http://www.amazon.de/s/ref=nb_sb_no...ld-keywords=Samsung+Galaxy+S2+USB+Jig&x=0&y=0 , plug it in, wait til its done and remove it again.
after that, samsung will never know i "messed" with the phone??
or do i have to consider/do something else?
tyvm!!
kws
I have the same issue.
When I was on my stock 2.3.5, I found a workaround:
- go into test mode (dial *#0*#)
- find the vibrate button, when you press it, it shouldn't work like you expect
- go back
- plug in your headphones and push the cable a bit to the left
- test vibrate again - this time it should work
- pull the cable out while vibrating, still pushed to the left, vibrations should stay on
I know it sounds crazy but it seems the hardware part that controls the vibrations is near to the jack port - excessive use of headphones, like it was case, must have damaged it somehow.
However, now I'm on CM9, so no test mode for me, I'm achieving the same effect by bashing the back button, so I get semi-constant vibration. I know, It's ridiculous.
Have the same problem here, I think it's software related because the shut down vibration stopped working when I flashed CM9 ICS, I can't remember if it was working anywhere else though. But now I'm back to 2.3.5 and it's not working at all. Did a Factory Reset, Cleaned Cache before and after the flash. Also used the Jig to reset my counter. Any clues?
I am experiencing the same issue.
Yesterday, I downgraded from 4.0.3 back to 2.3.5 as I was having a lot of problems with ICS. Now, my phone works fine again except for the fact that it does not vibrate anymore. (Which it did fine in 4.0.3 and before in 2.3.5)
I tried the trick Lechium06 mentioned in this thread but that did not work for me.
Anyone else having this issue? More important, anyone have a solution???
Greetinx
Johan
dajomas said:
I am experiencing the same issue.
Yesterday, I downgraded from 4.0.3 back to 2.3.5 as I was having a lot of problems with ICS. Now, my phone works fine again except for the fact that it does not vibrate anymore. (Which it did fine in 4.0.3 and before in 2.3.5)
I tried the trick Lechium06 mentioned in this thread but that did not work for me.
Anyone else having this issue? More important, anyone have a solution???
Greetinx
Johan
Click to expand...
Click to collapse
I saw something similar on CM9 thread, they said it could be a "bad flash", not a corrupted rom but the lack of proper cleanup before and after the flash. But I cleaned up everything before and after and I don't like reconfiguring the whole phone again for nothing.
it happend again.
dont recall what i did or if i did something last time at all. but it worked for over a year now. and now, my sgs2 doesnt vibrate at all, i tried all possible settings, tested with z-device and rebooted. nothing.
apprechiate any hint!
thx!!
kws
AW: [Q] Vibrate function doesn't work anymore, hardware issue
since i had that before, i ruled out a hardware issue. it happend when i played with the system settings. but as i sayed, i tried to reverse everything i did. now after i updated to 0206 and wiped cache and dalvik, still no vibration.
is there anything i could have missed?
is there a possibility to reset all settings to default without deleting all my data?
thx,
kws...
...tapatalking
kweso said:
since i had that before, i ruled out a hardware issue. it happend when i played with the system settings. but as i sayed, i tried to reverse everything i did. now after i updated to 0206 and wiped cache and dalvik, still no vibration.
is there anything i could have missed?
is there a possibility to reset all settings to default without deleting all my data?
thx,
kws...
...tapatalking
Click to expand...
Click to collapse
I assume since your posting in xda developers that you are rooted?
If so, just back up data with titanium backup app and factory reset, setup system and then restore USER apps and data only.
Sent from my GT-I9300 using xda premium
kweso said:
it happend again.
dont recall what i did or if i did something last time at all. but it worked for over a year now. and now, my sgs2 doesnt vibrate at all, i tried all possible settings, tested with z-device and rebooted. nothing.
apprechiate any hint!
thx!!
kws
Click to expand...
Click to collapse
Did you install another rom?
My vibration for example didn't work with some cm10.1 nightlies
it started in cm10.1 20130203. then i tried wipe cache and dalvik. nothing. then i updated to 0206 (wiped cache and dalvik again) > still nothing. went to bed. got up. everything ok! its vibration again! i am 100% sure, it did not work, when i left it on my desk last night. this morning, i checked for missed calls and it took a moment until i realized: i got haptik feedback back on patternunlock and keystrokes! checked ringtone-vibration: fine as well!
dont ask me how! would still like to know for myself.
thx,
kws
AW: [Q] Vibrate function doesn't work anymore, hardware issue
call me stupid!
suddenly this evening my phone stopped vibrating again. then i realized: quiet hours! i turned off haptik feedback at night.
could slap myself. at least ill find this thread again, next time i screw it again....
nite,
kws...
...tapatalking
Girls can use it again then. Good news for them!
Sent from the little guy
My camera all of the sudden stopped working the other day. Whenever I try to use it, the screen goes black then force closes after a few minutes. I tried to download a few other camera apps and nothing happened. Currently running with no root and I don't want to root it until the camera is fixed, unless that would help fix it.
MSK01 said:
My camera all of the sudden stopped working the other day. Whenever I try to use it, the screen goes black then force closes after a few minutes. I tried to download a few other camera apps and nothing happened. Currently running with no root and I don't want to root it until the camera is fixed, unless that would help fix it.
Click to expand...
Click to collapse
If you're on a 100% stock ROM with no changes and no root access with a camera that stopped working, there are very few things which can be done.
The only real solution would be to clear out the specific stock camera application's data directory. Not sure if this is possible w/o having to clear all the data.
I'd suggest the following steps in this order:
1) Manage applications under settings is where to look to clear out the specific Camera application data in hopes that only something was corrupted. Reboot and test.
2) Wipe all data on the device. Reboot and test.
3) If none of these worked, personally, I would return/exchange the stock device for another one as at this point, it would definitely seem to be hardware related.
An alternative route would be to gain root access and look into switch kernels/ROMs, but this could end up being a dead end if the issue is hardware related.
The only good/not so bad news is I've never seen the camera completely stop working on any of these devices .. at least not yet. So hopefully this issue is not hardware related! Good luck!
I cleared out the camera information and it worked the second I restarted my phone. Thank you!
That happened to me to, nothing I tried worked. Was good that I had ESRP. The Sprint store replacement the phone in lieu of just fixing the camera
dgr581 said:
That happened to me to, nothing I tried worked. Was good that I had ESRP. The Sprint store replacement the phone in lieu of just fixing the camera
Click to expand...
Click to collapse
Sometimes it's nice for them to just fix your phone and not give you a refurb. My sprint store seems to screw ur phone up when they fix it lol.
In the past when I was on the evo they swapped my screen out and broke my volume buttons. Then they just gave me a refurb.
Same thing happened to me. Suddenly, it doesn't work. Oddly enough, the Front Face camera does work by using the Mirror app. But the Rear camera does not respond when launching the Camera app.
I already tried switching ROMs, switching kernels, factory defaults, and nothing worked. Might be a hardware issue. I just hope it can be fixed without replacing my phone. It would suck having a replacement phone with HBOOT v1.50...
Does anyone ever have issues with the phone/dialer app?
If I try to call someone from contacts, I swipe on their name to the right and nothing happens, if I try again, I notice the contacts app has frozen OR I try to swipe again and nothing happens again. Eventually it might work after 2 or 3 goes.
Then I'll hang up after finally getting it to make the call and the phone immediately tries to make the calls I tried to make earlier... This happens fairly often but not all the time.
OR – (this happens rarely but does happen)
Phone rings, try to swipe the green answer thingo and it just bounces back to where it was, try to swipe/answer again nothing. I can't answer the call. Happened today, really pissed me off. Phone app crashed and refused to make a call after that for about a minute.
Sound familiar to anyone?
Using Android 2.3.5 Vodafone (Australia) stock unrooted.
Anyone?
Would love some help on this.
Yes I am facing the same issues as you.
A few observations:
problems exist on stock dialer app as well as third party dialer apps
It's an intermittent problem i.e. sometimes the problem shows and other times it does not
I was facing the same problem a couple months ago too, since i was running 2.3.3 so i had just upgraded to 2.3.6 and the problem had disappeared. But out of the blue it has again started now while i am running 2.3.6
Currently i am running on stock rom, cf rooted, latest modem.
Am looking for a permanent solution and will post a solution if i find one, in any case hope the official ICS release (due on the 15th) should solve the problem anyways.
Anyone else facing the same problem?
Updates
Usually clearing the cache and calvik cache does not help resolve the issue.
After posting the above post I had just created a ClockWork mod backup and Restored to the same. Dunno how but that resolved the issue, or to be exact, the issue did not surface for a couple days.
Today the issue actually became too much for me to be able to handle.
So I again cleared both cache and dalvik cache and then fixed permissions via CLockWork recovery menu.
Since then I am not facing the issue yet. Hope it works for you too.
(But this is just a preliminary observation and maybe the issue shall resurface with long term use)
p.s. really hoping that the impending ICS update will permanently fix said issue.
since last update 1.41 everything seems ok apart from when I am disconnected from internet via wifi or data themer crashes,as soon as I reconnect it is fine,anyone else have a similar problem ?
this only applies to any themes made in 1.41,any themes that are made in previous version do not require wifi/data access,can't believe just me having this issue.Have gone down the remove install but issue still persists.
alldroid said:
this only applies to any themes made in 1.41,any themes that are made in previous version do not require wifi/data access,can't believe just me having this issue.Have gone down the remove install but issue still persists.
Click to expand...
Click to collapse
Does it do it with version 1.42 as well?
not tried 1.42 yet will update when I get in from work and let you know
alldroid said:
not tried 1.42 yet will update when I get in from work and let you know
Click to expand...
Click to collapse
Did you try to Re-download your theme ? or try another ?
Just updated and problem seems to have vanished now,thanks to devs for quick solve
Problem not resolved yet.
I updated from 1.41 to 1.42 yesterday but the problem still persists.
Whenever i get disconnected from wifi or mobile data, i get to see an irritating pop-up every 1 minute saying: "The app found information about previous cashed. would you like to send this data to the developer?"
I have send it numerous times but it is still there. Its too much irritating.
I also tried uninstalling the themer app and deleting the my colorscreen folder, then restarted the phone and reinstalled the themer. But the problem is still there.
For additional information: This weird problem has started since addition of stupid "bollywood" category
yeah I just made a post regarding this as I now have the same issue m8,sent bloody loads of reports,and you are correct removing themer completely and reinstall does not work
the only way I have managed to get it working properly is to do a factory reset of the phone.Everything else including numerous deletes and reinstall does not work,I tried this as a last resort.Can someone let us know why themer seems to be holding onto the crash data,which as posted above is so annoying,and I or anyone else shouldn't have to factory reset to correct,Can this issue be looked into please by developers,as it can't just be the two of us having this issue.
Imranhakro said:
Problem not resolved yet.
I updated from 1.41 to 1.42 yesterday but the problem still persists.
Whenever i get disconnected from wifi or mobile data, i get to see an irritating pop-up every 1 minute saying: "The app found information about previous cashed. would you like to send this data to the developer?"
I have send it numerous times but it is still there. Its too much irritating.
I also tried uninstalling the themer app and deleting the my colorscreen folder, then restarted the phone and reinstalled the themer. But the problem is still there.
For additional information: This weird problem has started since addition of stupid "bollywood" category
Click to expand...
Click to collapse
alldroid said:
yeah I just made a post regarding this as I now have the same issue m8,sent bloody loads of reports,and you are correct removing themer completely and reinstall does not work
Click to expand...
Click to collapse
So for both of you, the problem only occurs when you get disconnected from WiFi/mobile data? Does this include going into Airplane mode?
We want to see if we can replicate this on our end.
ThemerSupport said:
So for both of you, the problem only occurs when you get disconnected from WiFi/mobile data? Does this include going into Airplane mode?
We want to see if we can replicate this on our end.
Click to expand...
Click to collapse
Yes, this includes the Airplane mode as well. (Obviously)
Yep as above and guess what factory reset does not solve it same problem this morning even though no errors in themer after reset,and agan plane mode is the same when not connected
Imranhakro said:
Yes, this includes the Airplane mode as well. (Obviously)
Click to expand...
Click to collapse
We're just trying to replicate the problem. There hasn't been anyone else with the same issue, therefore we need as much info as possible. I put my Nexus 5 on Airplane mode every night and haven't experienced the problem, hence asking the question.
ThemerSupport said:
We're just trying to replicate the problem. There hasn't been anyone else with the same issue, therefore we need as much info as possible. I put my Nexus 5 on Airplane mode every night and haven't experienced the problem, hence asking the question.
Click to expand...
Click to collapse
I assume there must be numerous people out there who might be facing the same issue, may be they are following this thread and just waiting for us to reach the resolution of the problem.
I agree with you that the more information will help you to diagnose the problem in better way, and I appreciate your support.
I own stock Samsung Galaxy Note 2 with Android 4.3. I''ll appreciate if "alldroid" and any other who is having the same issue, share their device info here.
Already did above somewhere m8 galaxy s4 running stock kitkat,it has to be themer related other wise the factory reset would have solved it.The only other solution is that the theme itself held on to the errors prior to remove and delete,but even if it did it is a themer problem imo as once an error log is sent it should be removed frm themers memory
Imranhakro said:
I assume there must be numerous people out there who might be facing the same issue, may be they are following this thread and just waiting for us to reach the resolution of the problem.
I agree with you that the more information will help you to diagnose the problem in better way, and I appreciate your support.
I own stock Samsung Galaxy Note 2 with Android 4.3. I''ll appreciate if "alldroid" and any other who is having the same issue, share their device info here.
Click to expand...
Click to collapse
alldroid said:
Already did above somewhere m8 galaxy s4 running stock kitkat,it has to be themer related other wise the factory reset would have solved it.The only other solution is that the theme itself held on to the errors prior to remove and delete,but even if it did it is a themer problem imo as once an error log is sent it should be removed frm themers memory
Click to expand...
Click to collapse
We'll keep searching to see if more people are reporting this problem. There is a huge update coming up, I'll see if the update is fixing this issue.
still have the issue and I refuse to believe only two of us have this issue,either that or we are the two most unluckiest themer app users in the world
latest update and..........problem solved no longer asks to send crash data when no net connection
No guys, you are not alone, I'm having this issue too anytime I disconnect my device from a wifi or mobile data, even during poor connection even though with the new update this should be fixed. I don't know if this happens in Airplane mode, never used that mode but I'll try and give you feedback.
Inviato dal mio macina caffè usando Tapatalk
see I knew we weren't alone,as above I have changed messed about with,used airplane mode and not had the error since the latest update here.Let us know if the update solves your problem m8