[Q] whatsapp can't get incomming messages at standby - Samsung Galaxy W I8150

When my nexus 5 (32GB rooted) is in standby mode, incomming messages can't be received - why?
When I wake it up it's get those messages that have sent to me before a long time (sometimes few hours).
How can I fix this?
I'm with stock rom...
By the way. is there better rom for nexus 5 than the stock rom?

Wrong Forum But Will Help You
NaNoNe said:
When my nexus 5 (32GB rooted) is in standby mode, incomming messages can't be received - why?
When I wake it up it's get those messages that have sent to me before a long time (sometimes few hours).
How can I fix this?
I'm with stock rom...
By the way. is there better rom for nexus 5 than the stock rom?
Click to expand...
Click to collapse
First of all, go to Wifi in the Settings Menu (the first on the list), tap on it, then tap on the 3-dot menu, there is an option called "Advanced", so tap on that and you'll get something like "Keep Wifi on during sleep", tap on it and choose Always. Even when screen is off but Wifi must be on, you will receive those text messages. As for your second request, best ROM or suggestions are not allowed on xda, if you want a ROM better than stock, you have to test something by yourself since performance and experience differs from one user to another (there are plenty like CyanogenMod, SlimKat, Beanstalk, ParanoidAndroid... etc).

Related

Keyboard does not type after unlock - Whatsapp

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!!!

Aokp and call delay

(Well... I wouldn't have gotten off stock had it not crashed and rebooted my phone periodically every dew hours...if anyone would like to help me out, please do - but I'm using AOKP now and the last kmsg on stock didn't show ANYTHING except for a watchdog error... but I digress)
In AOKP, despite the niggles there are (back/keyboard down arrow when in landscape), there is one odd thing I have noticed: say, my phone is sleeping and I get a call - the phone in the stock ROM would wake up instantaneously but in AOKP, it takes a minimum of a few seconds before I can decide what I want to do with the call.
Is there a patch available for this? Is there a workaround?
(I read CNA fixed the down arrow in landscape but the fact that the *#*#4636#*#* menu has been put elsewhere and that the dialer crashes when I type that sorta irks me ... but it might give me a reason to use that over AOKP if there's no solution to the call ringing delay problem).
BTW, no 3G here... all calls are on 2G, with or without WiFi turned on but with data enabled.
sent from my mini tractor

[Q] GMAIL Crash

Just received this SGN2 a few days ago. It's on Sprint and is running stock 4.1.2 and was never rooted or had any recoveries installed to it. I did a factory reset and installed my apps.
Whenever I get an email in the default Gmail app, I usually pull down the notification and tap it. Since I have box installed, it prompts me to choose the app I want to use to open the email. If I tap on Gmail and select just once everything works fine, but if I select Gmail then select always, my phone restarts(Boot animation etc...).
Has anyone encountered this at all or knows of a way to fix this? I'm thinking I should most likely go into stock recovery and clear cache or something. Don't know how that's going to help since this happened from a clean install.
Also, I have horrible battery life. WIFI off, BT off, 4G off(running 3G only), no S-pen detection, brightness on low, full cylce charge, but I still can't get the phone to output more than 7 to 8 hours of use. I don't think that I am such a power user. LOL. Will for find some other threads discussing about battery life on this thing.

[Q] What are the known bugs for VJ CM10.1 Jelly Bean 4.2.2?

Hey,
First of all I am a new member here on XDA forums and that is why I am asking you guys here since I really can't post on the actual ROM threads.
But anyway, what are the known bugs for the VJ CM10.1 Jelly Bean 4.2.2 ROM?
I am currently having problems with the ring tone and the loudspeaker option. Ring tone for the notification for Messaging does not play when I have received a message, I still have no idea why it is doing that.
As for the loud speaker, after a while it toggles off the loud speaker. It usually occurs when the display goes to sleep; I am not sure if it is supposed to turn the display off while on a call.
Thank you in advance.
Version 5.4.1 seems to have fixed notification sound and soft reboot issue. If you're on older version, suggest you to upgrade.
Other than that stock camera flickers (you can open, close and re-open to fix this) or use any alternatives from play store. Video recording is choppy.
Everything else should be fine as far as I know.
I flashed this rom yesterday, after three months with Nikez's JB. It's great.
I don't have problem with notification sounds, volume or whatever. But I just had the infamous "SIM added. Restart your device etc..." bug.
If you can deal with it (I can), it's a great ROM.
I have a call delay problem, I need to wait for 1 to 5 sec before start talking. Sometimes notification bar gets stuck, it starts working again after a while, but once I waited for more than 1h and decided to reboot phone. Also menu sometimes doesn't show up for random period of time.
That is all I noticed for now. I use 5.4.1.
One more bug - sometimes data access over mobile network doesn't work. I try to switch on, but do not get any network availability. Calls/SMS work, but there is no Internet connectivity. When I select automatic automatic network selection, then Internet starts to work imediateley.
Anyhow, this ROM is awesome! Thanks VJ!
codecs?
My First Post... Iuppy
After using CyanogenMod 7 and a infinity loop, I decided to use this ROM, and ... is working like a charm. However some videos that worked in CM7 are not working here. Had to install MX Player. Have I missing something or do I need to install some codecs? Even the preview on gallery are not working for some videos.
Pedro
I noticed when someone calls me its silent delay for like few seconds caller cant hear me and reverse.
Is this problem for all JB Roms or just on CM ,because i noticed that on AOKP to.
I am having problems with Clock location and also with downloading language pack for swype.
Use the thread in general section that VJ opened to discuss this. You'll get better responses.
Or even better, post in the main thread in the dev section.
tower9 said:
I have a call delay problem, I need to wait for 1 to 5 sec before start talking. Sometimes notification bar gets stuck, it starts working again after a while, but once I waited for more than 1h and decided to reboot phone. Also menu sometimes doesn't show up for random period of time.
That is all I noticed for now. I use 5.4.1.
Click to expand...
Click to collapse
Download CallDelayPatch?
Sent from my HTC Desire using xda app-developers app

Not receiving notifications unless I wake screen in OnePlus 3 running Marshmallow

Hi there, I was wondering if anyone might have any suggestions on how I could disable the Android Marshmallow doze/deep sleep mode that is default on new devices to save battery. I have a OnePlus 3 and have made every effort to check that all my notifications for calendar, whatsapp, emailing, etc. are set to both vibrate and make a sound, disabled all battery optimization features for apps, tried using screenlock wake apps to avoid missing notifications, and more. However, I am still unable to get notifications for whatsapp, emails, calendar reminders and events once my screen goes to sleep or I lock then phone and it's idle (so after about 15-30 minutes of it sleeping), but calls and texts seem to come through fine (or at least I haven't noticed these being an issue as much). This is a HUGE inconvenience, as my main reason to have a smartphone is so I can check emails, calendar events and such right as I receive them, and not only when I wake up my screen (which then bombards me with all my previous missed notifications from hours before). I have a feeling this is an android 6.0 issue and not due to the OnePlus 3, because it's been reported in other sites and by people with phones also using either this OS or lollipop. My older Samsung galaxy S4 running kitkat never had these problems, and at this point I'm very keen on going back if I can't get my new phone (or this OS, as I predict) to notify me right away even when my screen is locked and phone asleep (I can't always remember to check it especially if I'm busy at work). I am willing to root the phone and change settings if that's an option, but I would please like to see if you guys have any other suggestions for allowing my phone to receive notifications right away even when in sleep mode/idle/dozing. Thank you for your time in advance. Oh last thing, I also posted this question in other forums because I am honestly quite desperate to find out what I can do to resolve this issue, so I'm sorry if that's an inconvenience...
mblancoc said:
Hi there, I was wondering if anyone might have any suggestions on how I could disable the Android Marshmallow doze/deep sleep mode that is default on new devices to save battery. I have a OnePlus 3 and have made every effort to check that all my notifications for calendar, whatsapp, emailing, etc. are set to both vibrate and make a sound, disabled all battery optimization features for apps, tried using screenlock wake apps to avoid missing notifications, and more. However, I am still unable to get notifications for whatsapp, emails, calendar reminders and events once my screen goes to sleep or I lock then phone and it's idle (so after about 15-30 minutes of it sleeping), but calls and texts seem to come through fine (or at least I haven't noticed these being an issue as much). This is a HUGE inconvenience, as my main reason to have a smartphone is so I can check emails, calendar events and such right as I receive them, and not only when I wake up my screen (which then bombards me with all my previous missed notifications from hours before). I have a feeling this is an android 6.0 issue and not due to the OnePlus 3, because it's been reported in other sites and by people with phones also using either this OS or lollipop. My older Samsung galaxy S4 running kitkat never had these problems, and at this point I'm very keen on going back if I can't get my new phone (or this OS, as I predict) to notify me right away even when my screen is locked and phone asleep (I can't always remember to check it especially if I'm busy at work). I am willing to root the phone and change settings if that's an option, but I would please like to see if you guys have any other suggestions for allowing my phone to receive notifications right away even when in sleep mode/idle/dozing. Thank you for your time in advance. Oh last thing, I also posted this question in other forums because I am honestly quite desperate to find out what I can do to resolve this issue, so I'm sorry if that's an inconvenience...
Click to expand...
Click to collapse
Here is over 900 posts on this issue for your reading pleasure.
https://forums.oneplus.net/threads/push-notification-issues.451149/
Problem solved
Oneplus just released a new oxygen OS update which takes care of the notification issues. But to resolve this before this OTA came out I rooted and disabled the doze mode with dumpsys deviceidle. So all is good now!
mblancoc said:
Oneplus just released a new oxygen OS update which takes care of the notification issues. But to resolve this before this OTA came out I rooted and disabled the doze mode with dumpsys deviceidle. So all is good now!
Click to expand...
Click to collapse
Problem was NOT SOLVED with 3.2.1 OTA you still need to disable Doze in order to fix it.
Sent from my SM-T810 using XDA-Developers mobile app

Categories

Resources