Related
ever since the google voice update, with the widgets. Whenever I boot google voice the phone locks up for at least a minute before allowing me to click a message thread, then. When I load the message thread it locks up again for awhile before I can finally type the message. Exiting out causes the phone to lag a little bit on the homescreen. Any suggestions or others with the problem?
How large are your sms threads? It has been not breaking them up as frequently (or at all sometimes) as before, once they get above 300 or so for me the lag gets worse.
On the other hand, I've had it lag on occasion unrelated to that issue as well. I don't launch voice from the widget anymore, seems to usually lag more than if I just launch app from regular icon. Don't know why that would be.
Since installing the new version of voice it has been doing this to be all the time. Very annoying but I'm glad I'm not the only one.
Sent from my ADR6300 using XDA App
johnchad14 said:
How large are your sms threads? It has been not breaking them up as frequently (or at all sometimes) as before, once they get above 300 or so for me the lag gets worse.
On the other hand, I've had it lag on occasion unrelated to that issue as well. I don't launch voice from the widget anymore, seems to usually lag more than if I just launch app from regular icon. Don't know why that would be.
Click to expand...
Click to collapse
I erased all my messaging thread except two and it still lags. Both threads were 15 messages in size
I've experienced this too. I uninstalled and reinstalled and it seems to be a little better.
so I've had an issue with this for awhile and have no clue what's causing it. if i hit menu then the option for notifications it almost never opens the first time. started happening months ago on cm6 nightlies and I thought it was an issue with them at first but it's persisted through multiple full wipes and different roms.
when I hit notifications it'll either do nothing or start pulling down and stop and it usually takes 5-10 tries for it to work as intended. hitting menu and pulling it down manually is fine.
anyone else have this issue ever or know of a possible solution? I've tried full wipes a couple times and the only thing I haven't done is an ruu which I'll probably try later today.
bumping this in hopes of help
When I hit menu / notification, the menu just closes- nothing else no matter how many times I do it. I never noticed before because I use LauncherPro+ and have "hide notification bar" checked &when I want to see it I hit menu and swype the bar down with my finger manually- never use the notification button.
Are you using LauncherPro? I was thinking the glitch was from that since the button worked when I first got the phone and just used the Sense UI, no clue about launchers or rooting or ROMs. (I'm sooo much happier with my rooted, senselessrEVOlution, Lou's custom kernel 5, LauncherPro+, btw!)
Sent from my Incredible w/
Senseless rEVOlution
using XDA App
well just tested and looks like that's the issue lp+ and using the hide notification bar too. turned it to display normally and it works 100% of the time. thanks! gonna try and send a bug report to the dev.
I have a problem where, I am in a conversation in Whatsapp, and i am done writing a message, and then i lock the screen, and when i unlock it maybe 15 seconds later, i type, but nothing is showing up, its just records what i press but doesn't type. I have to go the the main screen, and reopen Whatsapp to get it working again...
Anyone else notice this?
Its really annoying if you are in an intense conversation and have to act fast
ROM: Codename Android 1.5.5
Kernel: FrancoKernel Milestone 2
I have wiped everything 1000x times and reinstalled everything. Found some people who had the same issue, but no one found a solution.
Thanks XDA,
David
Dubadai said:
I have a problem where, I am in a conversation in Whatsapp, and i am done writing a message, and then i lock the screen, and when i unlock it maybe 15 seconds later, i type, but nothing is showing up, its just records what i press but doesn't type. I have to go the the main screen, and reopen Whatsapp to get it working again...
Anyone else notice this?
Its really annoying if you are in an intense conversation and have to act fast
ROM: Codename Android 1.5.5
Kernel: FrancoKernel Milestone 2
I have wiped everything 1000x times and reinstalled everything. Found some people who had the same issue, but no one found a solution.
Thanks XDA,
David
Click to expand...
Click to collapse
Happens sometimes to me too and I am rooted on stock. Pretty sure it has nothing to do with us and everything to do with whatsapp having an ICS bug.
Sent from my Galaxy Nexus using Tapatalk
Whatsapp used to have exact same problem on my Nokia 5800XM too, I think it happens because of Whatsapp.
confirmed this happening occasionally on LG optimus one.
therefore, it is definitely because of the whatsapp app itself
usually i just press back button for once, back to conversation list and go back to my conversation. typing works back so you dont need to go homescreen thats two steps back
Confirmed bug for me too
Galaxy Nexus GSM
AOKP M4
Franco M2
To everyone who replied, thank you! Makes my life easier knowing its not ROM/Kernel etc...
Filed a complain to Whatsapp, such a great app apart from this bug!
Miasmic said:
confirmed this happening occasionally on LG optimus one.
therefore, it is definitely because of the whatsapp app itself
usually i just press back button for once, back to conversation list and go back to my conversation. typing works back so you dont need to go homescreen thats two steps back
Click to expand...
Click to collapse
I usually press home button and then my Whatsapp icon on my main screen, usually goes fast, but still... rather annoying
How deep would this 'error' lie? Could devs fix it?
I get this exact same problem with Handcent! Currently using Swype, and like 30% of the time I will have to go back to the conversation list and re-select my conversation to start typing again.
Sent from my Galaxy Nexus using Tapatalk
Quick question, is everyone using NovaLauncher too? It sometimes happen with normal SMS as well. But 95% of the time it is Whatsapp
ohh3nry said:
Quick question, is everyone using NovaLauncher too? It sometimes happen with normal SMS as well. But 95% of the time it is Whatsapp
Click to expand...
Click to collapse
I am also using Nova, but I'm not sure why that would affect other apps like this.
Any solution to this problem?
Got the very same at my galaxy s6, too. Android 5.1.1
I'd also like to know if there's any workarounds for this. My wife's having the issue and she's blaming me. :silly:
I may have a workaround. I have the galaxy note 3 and i use a custom rom thats pretty much close to stock and I notice that if I lock the device and unlock shortly after, I can't type anywhere, on kik, what'sapp, gosms pro, even google search. So I've just decided to test things out and see what's going on and here is what I found....
Eventually I can type again if I simply wait, but no one likes to wait but this is the longest solution.
Clearing the RAM using built in cleaner or 3rd party memory cleaner seems to allow me to type again.
I didnt like playing the guessing game in knowing how long to wait before I can type again so in kik or go sms pro, I would type one of the native apps' emoticon and then hold the backspace button down until it erases it...then I knew it was ready to let me type again (I have haptic feedback on for keyboard presses so I can look away as I hold down the backspace button - this would let me know when it eventually erased due to the haptic feedback of the smiley getting deleted).
Since the issue occurred only after unlocking, I tried turning off the lock screen completely and turning off phone and back on again....keyboard types right away with no issues!
Its more secure to have a lock screen on the phone so turning off lock screen isn't the best option unless you're like me and are the only person at home with no worries of someone else taking your phone so I decided to try something else that seemed to solve the issue, and that is..............turning off "Multiple Widgets" in lock screen.....tested and worked! I can totally type again right away after unlocking the lockscreen shortly after locking it.
This is what worked for me and for you developers out there....if you can use this to pinpoint why this happens on android, perhaps you can use this information to rectify it.
Hope I helped!!!
I'm not sure if I am the only one but searching hasn't really helped me find any answers. Basically, since updating (rather, doing a clean install of 4.2 tajku) to 4.2 Jellybean, I often have an issue where despite the fact that the proximity sensor blacks out the screen, the dial pad when pulled up still detects key hits. Hence, my cheek is randomly pressing buttons. Happens during voicemail since the dial pad is needed to get through menus and/or during calls which have a menu system.
Any else have this problem or have any ideas how I can resolve it?
Same here
Glad I'm not going crazy. Seems to also be happening without the dial pad, per say. I say that because it appears during a call, I was pressing something so I removed from proximity to be greeted by the lock screen (number pad). So I wonder if it has something to do with that. I am going to disable pin lock for awhile to see if that alleviates the problem.
Do you have something similar with SKype?
Do you have Skype installed?
I've something similar to this. When I am making a Skype call the screen does not go off during the call. It stays on and the only way I can make the call is to manually lock the screen before putting the phone over my ear.
You are the 5th person I meet complaining of this issue.
MenaMAKS said:
Do you have Skype installed?
I've something similar to this. When I am making a Skype call the screen does not go off during the call. It stays on and the only way I can make the call is to manually lock the screen before putting the phone over my ear.
You are the 5th person I meet complaining of this issue.
Click to expand...
Click to collapse
No Skype. And the screen goes off due to the proximity sensor - but the buttons and/or dial pad are still active. I'll try changing my power button back from "end call" to just screen off and see if that helps.
Anyway, a quick update. Seems like a couple of factory resets did the job. So something with Titanium Backup did not translate over well to 4.2 (from 4.1.2). On top of that, I can no longer seem to do a full restore, causes my device to go into boot loop. Don't know why it worked the first time. At any rate, just re-downloaded all my apps and so far so good. Just have to try and restore individual app data one by one and see if I can get it to stick without fudging up the dial pad again.
EDIT: Scratch that, it's going it again. What the hell... 4.2 is such a @#@#@ in the ass.
Still having same issue. Glad you came back with an update, bc I was about to re-flash and re-download all of my apps. I know you say that you experience it even without the keypad pulled up, but I have not. Usually happens when I call an automated system, and my call gets sent to every extension possible!
Sent from my Galaxy Nexus using xda app-developers app
Alright, I think I have it working. I did factory reset... made sure any phantom directories (i.e. storage(sdcard)/0/0/0/0 etc) were deleted.
1) By default, I tested by calling voice mail then rolling my cheek against the screen. So far so good.
2) I downloaded StickMount, Titanium Backup Pro, NTFS mounter (for ntfs driver) and ES File Explorer. Tested again as per above. OK.
3) Used Titanium Backup to restore missing apps + data. Did a test, still good.
4) Used Titanium Backup to restore only select system data (i.e. call logs, SMS log, alarm, etc). Still tests fine.
5) Enabled PGM free. Did test and BOOM, problem.
So it seems like with 4.2 there is something screwy with PGM which is essentially keeping the screen "awake" even though it's off due to sensor. Don't know why I didn't think of it earlier.
EDIT: Checked the PGM thread and it appears the author has already fixed it though only the paid version is updated atm. Says will update the free version soon if the paid version doesn't have any new bugs.
Awesome, nice work! Will see of it works for me too and report back.
Sent from my Galaxy Nexus using xda app-developers app
Edit Uninstalled PGM, reboot and its solved! Thanks for your hard work!
I was going crazy with this issue too .. it's good that it's not only me .. i will disable PGM and try
My brother's nexus has this issue without pgm installed on full stock 4.2.1 rom.
I have watched the serial code and production date is c9,or rather september 2012.
What I have to do to fix this very annoying issue?
edit: no one has this issue?It's a common problem of latest batch sold in Italy.
I searched the AT&T Galaxy S III General forum and saw no other posts similar. Essentially, I was wondering if anyone had experienced other bugs in the stock firmware. I am not rooted and have not modified my phone's software from stock.
There are two bugs I currently have seen. One I can and will provide screenshots of. This is where during the lockscreen the formatting will be incorrect, such that the last number on the time will be small and the charging text appears on the same line. Also note that the lockscreen shortcuts at the bottom are spaced oddly. I always have five icons, yet sometimes only 3 or 4 show spaced unevenly. I can reproduce this by watching Netflix and while a video is playing, I lock the screen. When I first unlock it, this will happen. This will fix itself if I relock the screen and wake the device again.
The second bug is in the messaging app. Sometimes when my device falls asleep by itself while I have the keyboard up and active on a thread, and I wake it, the keyboard is unusable. I can click on the message block to bring up the keyboard, but all of my keystrokes are not entered into the message block. I have to back out of the keyboard and thread, to the thread list, then go back to the thread. My previous keystrokes are still not showing, but the keyboard will then work.
Anyone else noticed any bugs?
I'm fine on my phone
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I've had the second bug happen with the keyboard maybe a handful of times since I got the phone but definitely not a regular occurrence.
I wouldnt worry too much about it but if it bothers you that bad just try a factory reset.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
No problems here
Sent from my SAMSUNG-SGH-I747 using xda premium
MercilessLTD said:
The second bug is in the messaging app. Sometimes when my device falls asleep by itself while I have the keyboard up and active on a thread, and I wake it, the keyboard is unusable. I can click on the message block to bring up the keyboard, but all of my keystrokes are not entered into the message block. I have to back out of the keyboard and thread, to the thread list, then go back to the thread. My previous keystrokes are still not showing, but the keyboard will then work.
Click to expand...
Click to collapse
I've only experienced this issue that you describe. I've gotten used to it, so I'm now indifferent towards it.
I've had issues with the battery life however and how the actual "percentage" is being reported, but I think that it's just Jelly Bean that is causing the issue when my device is restored to stock setup as opposed to running ICS. Sometimes, my phone gets really warm overnight (and I can assure you that nothing is running in the background). Looking at the battery graph, I see a sharp drop within the space of about 20 minutes. This causes the back cover of my phone to be discolored. My i747 is only 5 weeks old and I'm the original owner.
phone minimizes
I have an issue where my phone screen turns off when I'm it for a while (typically at work I use a wired headset). When I wake the phone up and swipe on the lock screen, the phone shows the phone "app" for a second then it jumps to the home screen (as if I hit the home button). Typically I'm unlocking the phone so I can either hit a number on the phone (like, press 1 for English) or I'm wanting to hang up. So I have to go back into the phone application to do either task.
ICS didn't do that to me.
Me and a few others have experienced a bug where the external sd unmounts itself at random. Mostly when the screen goes to sleep. For one freezing the MTP application with tibu solved his sd problem but by doing that you cant mount your phone to a pc. As far me nothing has helped yet. My external sd just unmounts at random and I have to remove it and put it back several times to get it to work again and sometimes and I have to format it in the pc to get it to work again. This has happened to a a lot of tmobile users. I never noticed this problem on ics so im assuming its a jb problem. Its not a micro sd card being bad because it does it with my other cards to and one is a very expensive Samsung card..
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
get2brad said:
I have an issue where my phone screen turns off when I'm it for a while (typically at work I use a wired headset). When I wake the phone up and swipe on the lock screen, the phone shows the phone "app" for a second then it jumps to the home screen (as if I hit the home button). Typically I'm unlocking the phone so I can either hit a number on the phone (like, press 1 for English) or I'm wanting to hang up. So I have to go back into the phone application to do either task.
ICS didn't do that to me.
Click to expand...
Click to collapse
I think this has happened to me once or twice. But I guess with the scarcity it's happened I thought I was bumping the back button or home button with my face, i.e. a failure of the proximity sensor to correctly detect my face.
I just started noticing the Keyboard Messaging bug myself. Wasn't sure why it was happening.
I just remembered (or refreshed my memory since my phone just started doing it) that whether or not TalkBack is off or on, my phone needs to tell me which number screen I am whenever I slide my finger across the dots at the bottom of the home screen or the app drawer. Is this a different setting I am missing or is this another bug?
I have had the messaging bug occur a couple of times. No biggee to me considering it has only happened twice in a month's time. I have seen other phones with much more persistent and annoying bugs and by comparison, this is nothing.
no problems here... i like it a lot now
Problem on Stock/root
Hey, not sure if this is the right place for this post, but my GS3 is on stock jelly bean and rooted. For some reason I am not receiving incoming calls. I tried calling my phone from gmail and the phone rings, but nothing happens on my phone. Any ideas as to why this is
Luker161 said:
Hey, not sure if this is the right place for this post, but my GS3 is on stock jelly bean and rooted. For some reason I am not receiving incoming calls. I tried calling my phone from gmail and the phone rings, but nothing happens on my phone. Any ideas as to why this is
Click to expand...
Click to collapse
I'm not sure if this is the right place either, since this is generally non-rooted, although the topic doesn't specify that I suppose.
However, I would venture a guess that you may need to wipe your data and cache. Sounds like a default app issue to me.
If I use bluetooth headphones on my walk to work, then plug in wired headphones at work, the audio plays out of the speaker.
It's really annoying because it happens every morning (as it's too early for me to remember things like that) and blasts my podcasts to my coworkers. Removing the wired headphones and reinserting fixes the issue.
No issues here.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I have never had any of these issues
Sent from my SAMSUNG-SGH-I747 using xda premium
miketigerwoods said:
If I use bluetooth headphones on my walk to work, then plug in wired headphones at work, the audio plays out of the speaker.
It's really annoying because it happens every morning (as it's too early for me to remember things like that) and blasts my podcasts to my coworkers. Removing the wired headphones and reinserting fixes the issue.
Click to expand...
Click to collapse
Actually, I've had a similar issue. I use Google Play Music (as a carry-over from my Nexus S). When the first song of the playlist would finish (using the headphone jack to play through my car stereo), the second song would start on the phone speaker.
It doesn't seem to happen anymore, but it did directly after the JellyBean update.
PIN Lock Instantly with power button
I am upset that the "Lock Instantly with Power Key" option missing from 4.1.1. I have been searching for a fix, but I must be the only one annoyed by this, or I'm bad at searching.
...
I have a pin lock but am used to a 15 min delay before I need to enter the pin, and being able to push power to shut the screen off at will. That is no longer an option as it always will lock to the PIN screen if the power button is pushed. It is very annoying to me.
Another bug is the Keyboard defaulting Samsung Keyboard on reboot. Every time I restart, I have to go back into settings to select Swiftkey.