Hello,
I've had my T-mobile SGH-T989 since March 2012. As it came with the standard Samsung Touchwiz loaded Android, I decided to flash a custom rom: Paranoid Android 4.4 RC2 (Android version 4.4.3), sometime back.
Ever since I have installed this new ROM everything except two things run very nicely.
1. I can use my camera, but only without any flash. The moment, I turn on the flash or put it on auto mode, the phone simply restarts. After restart, I can open the camera app, but the moment I try to take a picture with the flash on, it restarts. If I turn off the flash, the camera works without any problems.
2. Every time I am on a call, with me holding the phone to my ear (so that the proximity sensor detects that and turns off the screen to prevent accidental button press), after about 2 mins, somehow Google now gets triggered off and starts doing something on the screen (e..g opening browser, showing search history ,etc..) all the while I am talking on the phone. Off lately, approx since a week now, in addition to Google Now doing funky things, my phone now automatically goes to loudspeaker mode (even while I am holding the phone to my ear), and puts the phone on mute (although mute icon is not activated), but the other person can't hear anything.
It's just frustrating that I cannot talk without worrying about Google now triggering something off, or the phone going on loudspeaker and muting me off.
Can you guys please help resolve these issues? It's really annoying that a clean ROM like Paranoid Android is plagued with these problems, and I haven't been able to find an answer anywhere online.
Your help would be very much appreciated.
Regards,
Chintan.
Please help!
Hello Gurus,
I would really appreciate if someone can help me find out what the problem is with this phone.
Related
I've been using this phone for over a year w/o any problem but lately, since I last update some apps (and only apps, no android vers upgrade) my speaker phone seems to be glitchy. During calls, the speaker phone always turn on all by itself as if it was set on by default.
Is there anyway I can make the speaker phone to be the way it used to be? As in only turn on only when I tap the icon? Because I can't find any setting at all that deals with this.
A further info, there seems to be a glitch that the car panel apps also turn on by itself twice even without ever using any dock at all. Might it be if in car panel mode, the speaker phone was defaulted to on? FYI, I've never even used the car panel apps before, therfore it's strange that it does turn on out of a sleep/lock screen. I've turn off the auto launch so it never turn on again, but the speaker phone prob still persist.
Android ver 2.3.3 Sense 2.1 no rooting.
If the only solution is to hardreset, anyone know how I can save all my apps state so I can restore later? Installing the apps all over again seems to be a major headache.
Had that issue on my inspire, when ever i answer a call it would automaticaly go to speaker but i was rooted and on a custom rom. I unchecked quite ring on pickup , pocket mode, flip for speaker, and havent had the issue ever since
I've just try that, but sadly no, it's still doesn't fix it.
The only time it didn't turn on speaker phone was if I use ear phone.
I'll try to get 2.3.5 update and see if it help for now. But currently, the update still have't available yet.
Hello,
The screen of my moto 360 goes randomly off and vibrates at that moment, just like when you dim the screen with your hand., but now I'm using it. It's very frustrating because I can't even open an app normally or the screen goed of and I need to start over again. Does anyone know how to fix this?
Having same issues with mine.
Really strange and really annoying. Its like when u cover it with palm. It vibrates and screen goes off but ur in the middle of trying to do something. Anyone else having this problem?
Glad I'm not the only one having this issue, just got my Moto 360 today. I'll be in the Settings or other parts of the watch and it will just randomly turn off. It is really frustrating to deal with.
I have the same issue. I have pretty hairy arms so I wonder if the hairs are somehow triggering the capacitive touch screen.
you guys try to do a reset on the watch yet?? not just a reboot..
Any updates on this? I'm having the same issue
Any updates? I have the same issue I think it happend after udate to 5.0.2 but I'm not sure.
I'm also having the same problem. I picked up a new Moto 360 during the BBY sale rush of the last couple of days. At first it was buggy but the screen seemed to stay on while working with it. Then it had a system update, and since then most bug issues (like the faces not updating with the companion app changes) went away, however from that point the screen constantly shuts off, usually with a little buzz, while I'm interacting with the watch.
For instance, regarding the sensor used to turn off the watch if you palm it. I thought maybe that was it, so I was looking for a way to turn that off. I went into settings, and spend about 10 times of the screen shutting off before I could get to "accessibility settings" just to see if that might be there.
This problem occurs whether I'm wearing the watch or not (trying to eliminate arm hair or similar), and has occurred after a factory reset and re-pair with my phone (Note 4). Ambient sensor settings don't help, because all that does is make the screen go dark instead of off, but it still reverts back to the clock no matter what I was doing.
Any ideas? Any way to turn off a sensor perhaps, maybe in a custom ROM? Since this seems to be associated with an update near as I can tell, I wonder if a fix is coming from Moto or if it's too rare of an issue to be on their radar.
As an update, I replaced the watch with a new one, and this new watch is perfect. It started on outdated software which I left on for a bit to make sure it didn't show the problem, then I updated. Still no issues. I think there is a chance the problem is software regardless, but either way it must be a small portion of watches and isn't necessarily tied to any particular outside software influence (phone model or android version, or installed apps as NONE of those things changed). My advice to people reading this thread is to exchange the watch or get an RMA if possible.
Same Issue
Hi All,
I have the same issue. Sent it back for repair so let's see...
Same issue here as well
Hey all,
So I'm posting this thread regarding a couple pretty weird glitches and bugs occurring on my G3, 3 specific ones.
The first: (Probably the least serious but still REALLY annoying) At EXACTLY 12:00AM every night no matter what timezone I set the phone to (I'm in AU on the AEST GMT+10 timezone but it does this at the same time on any timezone) the phone will switch it's WiFi off automatically without warning, reason or explanation. It just goes off and then I have to manually turn it back on. Sure I could use an app such as Tasker or AutomateIt to turn it back on but I don't see why this is occurring in the first place?
The second issue (Most recent): Lately after updating to the V20E firmware for my D855 I've noticed that a graphical glitch (Specifically related to the colour Blue) occurs when there are fast moving elements on my phone's screen (Such as when I move a chat head around on my phone from Messenger, or when I'm scrolling Facebook or my App Drawer fast, there's just a blue box around whatever object/s appear to be moving on my phone's screen. I've not dropped the phone at all, and it has only been present since updating from the V20D ROM. Not sure what could be causing it.
The third and by far the MOST ANNOYING of the issues I'm having, is that for no apparent reason, whenever I am listening to Music with the stock Music player, and I lock the screen (The screen goes off) about 5 seconds later weird stuff starts to happen..
The song will pause, play or even stop completely, seemingly on its own. The "phone" will change songs, artists and sometimes complete albums and playlists completely by itself, with me doing nothing but staring at the lock screen (It keeps doing it until I re-enter the Music app, then when I lock the phone the whole cycle just repeats itself.)
I've done some looking around and careful observations on the phone itself, and it seems that before the weird stuff starts happening to my music, the phone opens Voice Mate by itself, and then if I'm not present, it apparently closes it and then that's when the stuff happens. I've tried everything I can on a non-rooted phone to stop this. I've tried re-installing the Music app, Uninstalling all updates to the Voice Mate and it's packages to the factory version, force-stopping Voice Mate, everything and no matter what I do the phone still opens Voice Mate and the weird stuff starts happening (It's like it's taking commands from Voice Mate to do something but I'm not even doing anything ) It's been doing this since I got my phone when it came with Android KitKat 4.4 (I was on the D10M ROM until I moved to the D20D Android L ROM) and I moved ROMs doing a completely fresh start ( I factory wiped the phone and then upgraded via a CSE flash and put all my stuff back on it manually) and I would've thought a completely fresh start would have fixed it but apparently not... Either it's a bug that's been present for a while, or it's something deeper than the ROM.
So yeah some pretty weird issues, if someone knows what could be causing them, please let me know, especially if you know a way to solve them.
Cheers guys.
I'm having a very similar problem with regards to #1 but it's doing it with Bluetooth for me!
At midnight on the dot, it will disconnect my connected Bluetooth devices. It doesn't shut Bluetooth off, it just drops the connection. I posted about it here: http://forum.xda-developers.com/verizon-lg-g3/help/bluetooth-disconnects-midnight-t2973187
Your phone sound possessed! Call 1-800-Exorcism now.
You right, weird/unusual.
Hello, I have had my Note 4 for quite some time now and have not had any issues with it up until the last month or so.
At first it started out as just a hiccup every now and then, an example would be when I play music via bluetooth to my Jeep CD Player, I would sometimes have to turn bluetooth off then back on to get it to connect or reconnect.
Now things are getting out of hand. Here is a list of problems I have on a daily/hourly basis and seemingly at random times. I cannot reproduce any of these problems (except the NFC problem) on demand.
I have noticed that rebooting the phone will clear up these issues (except NFC) for a short time, SOMETIMES. Other times a reboot does nothing to help the situation.
Keyboard Lag
Sometimes when I press the keys the phone vibrates indicating a key press and magnifies the key that is being pressed, but fails to enter anything in the text box/input field. For the record I am using Swiftkey. I have noticed that this happens most often when I open an app via "popup notification." For example, if I were to receive an IM or SMS I would tap on the notification that pops up, which then switches to/opens the corresponding app. It is then I will more often than not have this issue. To remedy this I have to close and re-open the app, sometimes several times causing the keyboard to open and close, several times... Sometimes when I TAP a key, the phone will behave as though I have held the key down or performed a "long press." This issue is not exclusive to the keyboard, it often happens anywhere on the screen and with any app, usually indicating that I have been "long pressing" for about 1-2sec at a time.
NFC Does Not Work
One day while I was at work I attempted to add the office printer via NFC. To my surprise I was unable to turn on NFC via the "quick settings" drawer. In the quick settings panel the NFC icon would light up, as if it were turning on, and then just turn right back off again, this happens consistently. I went into setting to enable NFC that way and I am stuck with a slider that is actually in the "on" position but greyed out, I am unable to interact with it.
Bluetooth Connectivity
I have a JVC CD player in my Jeep, I often use YouTube or Google Play Music when I drive. Usually I do not have any problems connecting to the CD player at first, but after about 30-60sec of playback the audio goes blank. The app says that it is still playing however no audio can be heard. Then it will suddenly come back on after about 5-10sec, and here is where it gets strange. After the audio comes back on after this "hiccup" the playback is fast, as in it is playing at 2X's it's normal speed, makes the vocals sound like chipmunks. This will continue indefinitely until I turn on the screen, unlock the phone, then shut the screen off. Then the audio goes on playing fine. This happens with both YouTube and Play Music, while using YouTube the video gets sped up as well. I also experience issues with connectivity where sometimes at random the phone will just disconnect from the CD player, and refuse to reconnect until I have rebooted the phone, or if it does reconnect I get no audio until the phone is rebooted. I notice that this ONLY happens when connected via bluetooth. If I turn bluetooth off while this is happening music will play over the phone's speaker perfectly normal. My CD player has a hands free feature, and I do not seem to have any issues with phone calls, it's only with music playback do I have problems.
Originally I thought it was my CD player acting up, however in light of the other problems, and the fact that I tested it with my tablet and two of my friend's phones without issue, I don't think the CD player is the problem.
Sluggish/Glitchy UI
Sometimes when the phone really freaks out, the UI behaves very strangely. Sometimes notification Icons will hover above the running app, other times the whole screen will lock in place for a few seconds. Sometimes if the screen is locked up, I will shut it off, then turn it on, shut it off, turn it on. However as I press the power button to turn the screen on and off, nothing is happening, the screen just stays black while the "back" and "recent apps" buttons light up at the bottom. Then when the screen does finally come back in it will flash on and off quickly in accordance with how many times I pressed the power button. While all this is happening, if I hold the power button to turn the phone off, the power/reboot menu will appear without incident. Sometimes when I am swiping to unlock the phone, it does not register the full swipe. Basically it acts/appears as though I lightly touched the screen and moved my finger a half inch even though I have drug my finger all the way across the screen. To remedy that issue I have to SLOWLY drag my finger across the screen and then it unlocks without incident. I have also noticed that when I go to "swipe away" a notification, especially one that has "information" in it, it will swipe off the information but leave the notification there and display the app name the notification was from. An example would be, if I just installed an app (for example YouTube) from the Play Store, the notification will say "YouTube has been successfully installed." When I swipe either left or right to remove that notification, a "white ghost box" or "overlaying top layer" with the "successfully installed" text in it will slide away. However it leaves behind a green box/notification that says "Google Play Store" and that remains until I shut the screen off and turn it back on.
NFC Will Not Turn On
I simply cannot get NFC to turn on, the slider is in the ON position but is greyed out as I mentioned earlier. I would post a picture but I guess there is a 10post rule before I can do that. I have given up on NFC, mostly because I rarely use it, so it's really not that big of a deal.
Initializing the Camera
I use an app called "Telegram" instead of SMS messaging, thus I use Telegram to share pictures with friends. Sometimes, again I am not able to reproduce this problem on demand, the problem comes and goes seemingly at random. The camera will take more than 30-60sec to initialize, while I am waiting for it I am stuck with a black screen. If the camera doesn't initialize, shutting the screen on then off will take me back to the telegram app. I never get an error message or anything. Other times when I try to use the camera it pops on instantly and works flawlessly. Originally I thought this was a problem specific to telegram, however in the name of science I tested it with the default camera app and get the same results.
USB File Transfers
I'm not really sure this is specific to my phone, but whenever I transfer files from my PC to the phone or from the phone to PC, it is PAINFULLY slow. It's even painfully slow when the PC just displays what is in the folder. However I can't say for sure this is related because I never attempted to transfer files until I started having these issues, at which point I thought it would be a good idea to start backing things up.
Gets Stuck in 3G Mode
This happens rarely, not even sure that it's related but I felt that it was worth mention.
What have I done to try to remedy this problem you ask?
So far I have performed a non-root ADB nandroid backup, just in case factory resetting the phone didn't work.
I have factory reset the phone 2 times, I see no improvements.
I have cleared out my SD card/removed SD card
I removed and/or shut off bloatware apps (Yes I tested the phone without removing/disabling bloatware, still having the same issues)
Wiped cache via Recovery
I am not sure what else I can really do to fix the phone, I am starting to think that this is a hardware issue. I should mention that there was no significant event that I feel would cause these malfunctions. System update installed and worked perfectly up until this last month, I have not dropped the phone from significant height, the phone has an otterbox anyway. I have not gotten the phone wet, it has not been left outside, this phone has not seen any abuse what-so-ever. I just started having these problems out of the blue and they seem to be getting progressively more frequent and longer lasting. If I don't get any ideas from here I am going to try to get Verizon to replace the phone via insurance, however I don't have high hopes for that because I have grandfathered unlimited data and this is not the "original" phone that I had when I added the insurance option, so I am not sure it's covered.
Does anyone have any ideas on what could be causing this or anything I can do to correct it or try to troubleshoot it?
Any help is greatly appreciated!
Phone Information is as follows:
Samsung Galaxy Note4
Model: SM-N910V
Android Ver: 5.0.1
Baseband Ver: N910VVRU2BOG5
Build#: LRX22C.N910VVRU2BOG5
HW Ver: N910V.05
Verizon Wireless
Non-Root, Default Launcher, Not modified in any way.
I realize that this is a long post but whenever I ask for help I like to be detailed. If I left out any information that might be helpful please let me know.
Unfortunately, it looks very much like components on your logic board are going bad. Sometimes a few specific things will go bad that don't actually make the phone unusable, but make it act similar to what you are explaining. It wouldn't be worth the money you'd have to pay someone to track down the bad components and replace them. If you really like the note 4, I would just make a full backup with kies while you can, buy a new phone and restore your backup.
All of Kies backups do NOT restore to a new phone! Only contacts, messages and call logs will restore on a new phone. Use Samsung Smart Switch or Helium. Good luck
Sent from my SM-N910V using Tapatalk
outcasted2003 said:
All of Kies backups do NOT restore to a new phone! Only contacts, messages and call logs will restore on a new phone. Use Samsung Smart Switch or Helium. Good luck
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
I see. I didn't know that because I've always restored my backups to the same phone. Thanks for the info.
I have a weird issue with my A2 Lite.
I tried couple of ROMs so far and it's all the same.
When I receive a call and answer it, I bring the phone to my ear and I can see that display goes off - that's good. But, despite keeping the phone close to my ear, the flash light turns on, bt or even airplane mode so it disconnects the call, it changes the screen brightness or mutes the mic during the call. It's like touch sensor was alway on with display off, so I can't even see what I'm touching and switching.
I even went back to stock MIUI to be able to run system check with *#*#64...etc. and proximity sensor works fine.
My problem is similiar to this one: https://forum.xda-developers.com/mi-a2-lite/help/lockscreen-notification-sound-proximity-t3867872.
This drives me crazy!!!
Did anyone have this problem or knows some tricks to fix it (beside smashing the sh..t on the wall)?
I experience the same thing sometimes with stock rom
keyone72 said:
I experience the same thing sometimes with stock rom
Click to expand...
Click to collapse
That - I didn't expect...
But it has to do something with the Android or kernel maybe. How does it come, that screen is being turned off but not locked (meaning insensitive for touches)?
Weird...
And I'm almost sure, it wasn't like this before... before I installed one of custom ROMs (Arrow maybe). But since then I even went back to stock Pie, so if any firmware/kernel manipulation caused it, with stock - it should've fixed.
I'm starting to dislike daisies...