Related
Is anyone else having a problem with auto orientation taking a dump every once in a while? It's happened 2 if 3 times since I got the phone on Wednesday...
I end up having to reboot.
Chris
Sent from my Inspire '4g'.
Yep happens to me.
Sent from my HTC Inspire 4G using XDA app
Yeah it happens to me too...
Hasn't happened to me yet. What, does it just stop rotating or something?
it will stop rotating, and when porgrams like browser, or reader, are opened they are rotated the wrong way, and will not change.
But once rebooted all is normal again.
Weird, happened to me a few days ago too. I couldn't get anything to
rotate...music, browser etc. After reboot it's been fine.
Mine has done it 3 times so far. A reboot fixes it, but it's still lame.
Nope hasn't happened yet. Had a Bluetooth bug where it wouldn't turn on but reboot fixed that.
Update happened to me now. Many software cause it dosn't happen in all software at the same time.
Sent from my Desire HD using XDA App
Happened to me the first day I purchased it...the browser was stuck on landscape and pictures I took were wrong orientation...I was freaking out a little bit but a reboot fixed it.Happy now Hasn't happened since.
sent from my HTC Inspire™ 4g using XDA App
Mine just did this for the first time. I'm using ADW EX launcher. You folks with the issue using alternative launchers?
It happened on the demo unit at the AT&T store. The salesguy said he never saw it before. hahaha!
Hasn't happened to me.
Sent from my Inspire 4G using XDA App
No, I'm running complete stock at the moment(waiting till my trial period ends before I root and start playing; coming from the vibrant on unlimited data t-mobile.... love the phone so far but not loving the whole 2gig thing)
My auto rotate has died almost once every day... but when it does it still worksin the browser. Strange. Certainly software.
Sent from my Inspire '4g'.
has anyone found a fix?
Some of what I am seeing reminds me of times I had a bad flash.
Just did a factory reset, and if that does not work will try reflash using the RUU.
It's done it to me twice in the week since I got it - still using stock OS. Restart seems to fix it. It's a little aggravating, but nowhere as bad as all the crashes I had with the Atrix before I traded it back for the Inspire.
It seems to be in the kernel. When I made my custom kernel it did that all the time, has something to do with the Auto-rotation configs. I believe a kernel compiled from our newest sorce fixes this, at least I'm pretty sure.
It happens to me every time I have a LWP enabled that use the accelerometer, like galaxy core and metal rain. Selecting another LWP or disapbling the feature in the LWP solves the problem for me. I saw this behavoiur in the stock rom, tpc's rom and ar 3.2rom.
Happened to me a little after flashing coredroid when all the roms started coming in. Reboot fixed it of course. I remember frantically toggling the auto rotate and fearing a dead orientation sensor.
Sent from my Inspire 4G using XDA App
It's happened to me in the past too. I did notice that the problem stopped when I stopped using the "reddit is fun" application though, and it hasn't happened ever since. Maybe the problem lies within certain applications? Could just be a coincidence. Might try using the app again later to see if it happens again.
DOAlaboratories said:
It seems to be in the kernel. When I made my custom kernel it did that all the time, has something to do with the Auto-rotation configs. I believe a kernel compiled from our newest sorce fixes this, at least I'm pretty sure.
Click to expand...
Click to collapse
Don't know, it happened to me 2 times when bone stock not even rooted, didn't happen at all on my rom/kernel until last night with my kernel which is latest source, unless there was some new source posted in the last few days, but I don't think there has been since there's been no update.
Maybe it is hardware.
Either way its completely random
Hey Everyone,
I am having some issues with my Nexus S (GSM). This does not happen on the stock rom but it seems to happen on any rom I flash and it becomes very annoying. The phone would be operating normally and out of nowhere it stutters and becomes extremely slow for about 5-10 seconds after it which it vibrates twice and back to normal again. I have also noticed that if the phone is idle it almost always goes through the slow process once I start it up.
If I increase the cpu to 1.2 ghz or higher the problem seems to appear more often.
I am hoping someone will help me fix it because the problem is extremely annoying when it happens during voice calls as it cuts out and the other person cannot hear me. If not I guess I will have to sell it.
Anyone have any solutions or has the same issues?
I think I had the same problem from time to time, but only when I was using a case on my phone.
I would unlock the screen and the device would be super slow for a few seconds, then I'd get a couple of quick vibrations and it would be back to normal.
My guess was that the case was pressing one of the buttons in (maybe volume?) while unlocking and it somehow caused the retardation.
I haven't seen that problem since removing the case -- though maybe it was a coincidence and I'm using a different rom that fixed it? Not sure.
In any event I'm using NSCollab 1.0.39 if you want to give it a try.
Are u doing fresh installs when u switch between roms
Sent from my MIUI powered Nexus S 4g using XDA Premium App
mizunox said:
I think I had the same problem from time to time, but only when I was using a case on my phone.
I would unlock the screen and the device would be super slow for a few seconds, then I'd get a couple of quick vibrations and it would be back to normal.
My guess was that the case was pressing one of the buttons in (maybe volume?) while unlocking and it somehow caused the retardation.
I haven't seen that problem since removing the case -- though maybe it was a coincidence and I'm using a different rom that fixed it? Not sure.
In any event I'm using NSCollab 1.0.39 if you want to give it a try.
Click to expand...
Click to collapse
I already have tried and still no success. Usually when i restart the phone it fixes it temporarily but it comes back after some time.
I wipe the data, cache and dalvik cache every time I flash a new rom. So yes it is a fresh install...
Sent from my Google Nexus S using XDA App
Anyone else with any ideas on how to fix it?
Sent from my Google Nexus S using XDA App
Hi all,
Since updating my O3D to the latest firmware via the LG Update tool, it has crashed a few times (at least three), so bad that I had to reboot.
It happens when I use the keyboard. Twice while typing text messages and once in Dolphin web browser.
Keyboard and messaging app were the stock ones from LG.
It seemed like the keyboard 'app' crashed and wouldnt respond to presses any more. I could press the home button at the bottom of the screen, but the keyboard stayed on screen taking up space and everything move up to the top. If I held the home button I could switch apps but noting worked. Eventually I just held the power button and powered off. I had to choose power off twice before the phone did anything.
This was the same each time it crashed.
Anyone else seen problems like this? Never saw it before I updated the fw but then again I've only had the phone a couple of weeks.
This is my second update since having my Optimus 3D and yes this time I have noticed one problem that I didn't have before which is that if I leave my wi-fi enabled then the phone will reboot after about twenty minutes of it being on yet if I switch the phone off the phone works fine.
So yes it is possible the firmware update affected your phone in some way. In your case you could try a different keyboard app but in mine it is the built in wireless so no solution as yet but maybe a keyboard app and or alternative messenger app will help solve your problem.
Dave
I'm running stock v10k and my camera will only run after I kill everything with atk and also my goto lock screen is constantly asking me to force close is it 10k update doing this.
Sent from my LG-P920 using xda premium
Cav3 said:
I'm running stock v10k and my camera will only run after I kill everything with atk and also my goto lock screen is constantly asking me to force close is it 10k update doing this.
Sent from my LG-P920 using xda premium
Click to expand...
Click to collapse
I don't think its v10k doing this. I believe its ATK doing this.
Sent from my LG-P920 using XDA App
same here I had problems once I updated from D to K and then 10J, the phone will just keep rebooting, I tried taking out the SD card as some have suggested but that still did not fix the issue, last night I totaly wiped the phone to Brand new condition, then re-installed everything via the market, No root and the phone so far has been working perfect, 14 hours no reboots with wifi set on always.
after updating to LGP920-V10k-SEP-17-2011 my phone reboots ever 20 min.
phone is completely wiped no root. just standard.
Not sounding good. I do have root on my phone and I also leave WiFi on from when I get home until when I go back to work and my phone doesn't reboot on its own.
The last time my phone crashed was Friday or Saturday but I havent used the keyboard that much since.
anielk77 said:
after updating to LGP920-V10k-SEP-17-2011 my phone reboots ever 20 min.
phone is completely wiped no root. just standard.
Click to expand...
Click to collapse
Maybe they are different revisions of the motherboard on the phone.
It is strange to help because i don't have any reboots.
Another thing I have noticed since the update, when typing text messages if I turn the phone to landscape mode, the screen doesn't rotate to match.
I have a few rotation glitches too I think they need to hurry up with GB update
Sent from my LG-P920 using xda premium
To be honest, I didn't check into the whole Android version thing before I got the phone and it never bothered me, until now! Hopefully these bugs wont be present in GB.
cyberguru said:
To be honest, I didn't check into the whole Android version thing before I got the phone and it never bothered me, until now! Hopefully these bugs wont be present in GB.
Click to expand...
Click to collapse
I am in gb so guess the bugs are universal but solved my wifi issue by setting wifi to sleep when phone screen is off.
Dave
My SGR has stopped vibrating, regardless of the setting. I noticed it about an hour ago.
I can confirm that it was working about 12 hours ago.
I am running InfectedROM V1 on ardatdat's keenal v1.5
Anybody got any ideas what is wrong?
Sent from my GT-I9103 using XDA App
I can't understand what could have caused this, did you bump /drop you handset anywhere recently ? If yes then it can be some hardware issue.
Check your recently installed apps, they maybe interfering with the vibrator settings though that's a remote possibility but do check.
If its a software bug then flashing the ROM/kernel again should solve the problem. But keep this as the last option if it seems there's no other way out.
It started working. On its own.
I had it in my pocket, got a text and it vibrated.
Funny issue. I can't understand what happened. But I am glad I don't have to take it in for servicing.
FeralFire said:
It started working. On its own.
I had it in my pocket, got a text and it vibrated.
Funny issue. I can't understand what happened. But I am glad I don't have to take it in for servicing.
Click to expand...
Click to collapse
That's good !
I think it must be a software bug which caused it then.
It was solved as you may have restarted your handset but still do observe if it stops vibrating intermittently.
Actually I did a soft reset when I noticed it, that did not fix it.
I tried changing the vibration settings randomly and all but nothing worked.
I have got no idea what happened. But I have been checking the vibration every hour or so and it hasn't stopped working after that.
It has stopped vibrating again.
This is so irritating. I miss calls and texts because of this.
Sent from my GT-I9103 using XDA App
FeralFire said:
It has stopped vibrating again.
This is so irritating. I miss calls and texts because of this.
Sent from my GT-I9103 using XDA App
Click to expand...
Click to collapse
Darn !
That's why I told you to monitor it. Now I think it could be a software issue. If it was a hardware one then it shouldn't have started working again.
Check if a restart solves the issue. Do remove the battery for a few secs before switching it on again.
If it works its a software bug.
Did you check the installed apps if they are interfering with the settings ?
Do check the settings for Vibration intensity if they are at default.
Check and reply here buddy though I think you'll need to take it to the service center if even flashing stock ROM doesn't solve the issue.
I finally found out the problem and the solution. Was googling about it and a guy with SGS2 had posted on some forums that his vibration stops working after removing headphones. He also gave a solution to change the vibration settings to 'never' and back.
I tried that but it didn't work.
Then I tried replugging my earphones and the vibration immediately started working.
I don't understand what could be causing this issue but atleast I got a fix now.
Seems software related as you said. Maybe it is fault with either the customROM or the custom kernel. Would be pretty weird to have bugs like this in stock.
FeralFire said:
I finally found out the problem and the solution. Was googling about it and a guy with SGS2 had posted on some forums that his vibration stops working after removing headphones. He also gave a solution to change the vibration settings to 'never' and back.
I tried that but it didn't work.
Then I tried replugging my earphones and the vibration immediately started working.
I don't understand what could be causing this issue but atleast I got a fix now.
Seems software related as you said. Maybe it is fault with either the customROM or the custom kernel. Would be pretty weird to have bugs like this in stock.
Click to expand...
Click to collapse
There are no such bugs on Samsung stock ROM.
You'll need to request #ardatdat & #eaglerazor12 to look into the issue and they will definitely help you.
It has stopped wirking, yet again and no matter what, I can't revive it.
I have even flashed everything stock except for the recovery. [Is there anyway to go back to stock recovery?]
Sent from my GT-I9103 using XDA App
FeralFire said:
It has stopped wirking, yet again and no matter what, I can't revive it.
I have even flashed everything stock except for the recovery. [Is there anyway to go back to stock recovery?]
Sent from my GT-I9103 using XDA App
Click to expand...
Click to collapse
Wish I could help buddy but I have no idea about that.
Ok.
Thanks.
Atleast now I can be sure that it is a hardware issue. Will have to get it fixed one way or the other.
Sent from my GT-I9103 using XDA App
u get stock recovery automatically when you reinstall your fw.
m.kochan10 said:
u get stock recovery automatically when you reinstall your fw.
Click to expand...
Click to collapse
I reflashed my nandroid backup through CWM to get stock back. Should I flash it again through Odin?
Sent from my GT-I9103 using XDA App
actually no, but if you have your fw u may take recovery from the package and push it to another tar file (use total commander) and then just flash it via odin.
http://www.youtube.com/watch?v=3JA3PXNYjJM
This fixes the problem.
I feel really angry at Samsung for making the SGR with the same fault that SGS2 had. Why not fix it if the already had complaints about it in the previous phone?
Atleast I don't have to take it to the service center now.
I've seen several posts in different ROM threads talking about proximity sensor issues, and I think I have your fix.
Awhile ago, back when I was on CM10, I noticed that my proximity sensor was no longer functioning as expected. The screen would remain on when I was on phone calls, and would stay black for long periods of time after hanging up.
I initially chalked it up to a CM10 issue, but when I flashed back to a Sense ROM, the issue remained. Eventually, I discovered this app...
https://play.google.com/store/apps/details?id=com.incredicontrol.ProxSensorCalibrator&hl=en
...and it worked perfectly.
The best thing to do is start up the app and see if it says "NEAR" or "FAR" at the bottom, then move your hand close and further from your phone to see when it changes. To be completely honest, I don't entirely understand what the settings in the app correspond to - I just played with the settings until the "NEAR" and "FAR" labels appeared at what I believed was the correct time. The attached screenshot shows the settings that ended up working for me.
Sure enough, I have no proximity issues now - except when I recently flashed LiquidSmooth, and forgot to re-run this app. As soon as I re-calibrated, it worked great again. So, this fix isn't permanent - you have to keep this app installed, and it has to be set to run on boot. You also have to have root for it to work its magic.
Hope this helps some of you out there!
Thanks for the info. I'm definitely going to give this a shot. I've had issues like you had on all 4.2 ROMs with s2w. My issue does go away when I go to something different though. Still gonna give it a whirl though and see if it helps.
Oh well, it doesn't look like my calibration is off. Thanks for the suggestion though.
Sent from my One X using Tapatalk 2
pside15 said:
Thanks for the info. I'm definitely going to give this a shot. I've had issues like you had on all 4.2 ROMs with s2w. My issue does go away when I go to something different though. Still gonna give it a whirl though and see if it helps.
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Yeah, I think the s2w bug may be something different entirely, but it can't hurt to check.
Silellak said:
I've seen several posts in different ROM threads talking about proximity sensor issues, and I think I have your fix.
Awhile ago, back when I was on CM10, I noticed that my proximity sensor was no longer functioning as expected. The screen would remain on when I was on phone calls, and would stay black for long periods of time after hanging up.
I initially chalked it up to a CM10 issue, but when I flashed back to a Sense ROM, the issue remained. Eventually, I discovered this app...
https://play.google.com/store/apps/details?id=com.incredicontrol.ProxSensorCalibrator&hl=en
...and it worked perfectly.
The best thing to do is start up the app and see if it says "NEAR" or "FAR" at the bottom, then move your hand close and further from your phone to see when it changes. To be completely honest, I don't entirely understand what the settings in the app correspond to - I just played with the settings until the "NEAR" and "FAR" labels appeared at what I believed was the correct time. The attached screenshot shows the settings that ended up working for me.
Sure enough, I have no proximity issues now - except when I recently flashed LiquidSmooth, and forgot to re-run this app. As soon as I re-calibrated, it worked great again. So, this fix isn't permanent - you have to keep this app installed, and it has to be set to run on boot. You also have to have root for it to work its magic.
Hope this helps some of you out there!
Click to expand...
Click to collapse
Thank you. I hated hitting the wrong button with automatic machines. Will try this out. I am also on liquid smooth so I may try the same settings. Thanks!
Sent from my One X using xda app-developers app
solving with
Proximity Sensor Fix
Worked for me! Thank you
Hitting the thanks button is probably enough, rather than digging up an old thread by commenting on it.
Sent from my Evita
My Device: HTC One X
There are problems with the proximity sensor.
The application worked fine. Thank you very much.