Any notifications I get such as New messages on what app or Facebook posts only Notify me the instance I wake the device. This only happens when connected to wifi. I tried multiple access points too. This never happened to me when I was running a month old cm10.1 rom but now any rom I flash has this problem. Currently running AOKP. It's so annoying when your phone doesn't vibrate when you get a new message until you actually turn it on. Any suggestions?
Sent from my Nexus 4 using xda app-developers app
Make sure WiFi sleep policy is set to always.
Sent from my Nexus 7 using Tapatalk HD
Yeah it is lol
It seems to be fine on latest nightly of cm still happens on other roms though
Sent from my Nexus 4 using xda app-developers app
Are the roms with the problem using a custom kernel/boot.img ?
Back when it worked a month ago, I was using francos kernel. Now I'm running cm with whatever kernel it comes with and it seems to be working. AOKP or PA still have the lag issue.
Sent from my Nexus 4 using xda app-developers app
For me I've noticed push notifications don't work on any kernel that has the wakelock fixes when using WiFi with the screen off on any message type app I have tried, though gmail does work. Older custom kernels or the original kernel work fine.
Maybe your error is similar?
You might be right. Any idea if the kernel for PA or AOKP include these fixes? And does Franco kernel include these fixes?
Sent from my Nexus 4 using xda app-developers app
Franco kernel introduced the fixes at much the same time as all the other kernel devs, you would to look at the respective change logs to see at what revision the fixes were implemented.
With franco kernel r34 notifications are fine over wifi.
Regards.
It's known issue, not a kernel/rom, Google's fault!
calanizzle said:
It's known issue, not a kernel/rom, Google's fault!
Click to expand...
Click to collapse
No its not, stop saying it everywhere. Original boot.IMG and other kernels pre wake lock fix work fine. I was a using message apps faultlessly for a whole month before kernels with the wake lock fixes came out
meangreenie said:
No its not, stop saying it everywhere. Original boot.IMG and other kernels pre wake lock fix work fine. I was a using message apps faultlessly for a whole month before kernels with the wake lock fixes came out
Click to expand...
Click to collapse
Sorry to say but Franco himself said this was Nexus 4's fault...
Don't care what franco said, with non wake lock fix kernel my message apps work fine with wifi/screen off, with wakelock fix kernels they don't... black and white. And it's not a wifi problem here because gmail syncs work fine all the time whatever kernel.
How do you account that i used them fine for @ month ? and still can if i flash a non wakelock fix kernel... but i'm guessing franco made no such absolute as you claim.
It's not Googles fault. Stock rom works flawlessly so does the latest cm build.
Sent from my Nexus 4 using xda app-developers app
FYI. whatsapp been lagging on my iPhone 4 for a while too actually on 5.1.1 (i think)
It doesn't lag at all on cm or stock
Sent from my Nexus 4 using xda app-developers app
meangreenie said:
No its not, stop saying it everywhere. Original boot.IMG and other kernels pre wake lock fix work fine. I was a using message apps faultlessly for a whole month before kernels with the wake lock fixes came out
Click to expand...
Click to collapse
Uh, yeah it is. The WiFi driver cannot offload ARP broadcast requests, so Google chose to have the phone disregard ARP requests, most likely to reduce power usage. Have you ever had a device that can't be pinged when in standby? Now you know the reason.
The driver will be updated in a future release. You can sidestep this problem on a dd-wrt router by assigning a static IP addresses to the device.
If you receive emails always on time, then you are lucky that you have a router whose ARP cache timeout is unusually long, at least longer than Google's heartbeat which is set at 15 minutes. Using mobile data does not apply to any of the above.
Sent from my Nexus 4
Related
Good day, what is the current status for your nexus s self rebooting issue ?
No reboots whatsoever
NSCollab 60 with latest Franco kernel, 110 liveOC with a little undervolting, Deep idle enabled.
None
Sent from my Nexus S 4G using Tapatalk
There is a reboot issue?
Sent from my Nexus S
DZG said:
Good day, what is the current status for your nexus s self rebooting issue ?
Click to expand...
Click to collapse
None... there is no issue. That said if you under volt too much...
Bounced off a tower to a forum near you!
Non existent.. ASOPs ICS running strong
Sent from my Nexus S 4G using xda premium
http://www.google.com/support/forum...4f&hl=en&fid=1b777a366748b64f0004b3418a290418
DZG said:
http://www.google.com/support/forum...4f&hl=en&fid=1b777a366748b64f0004b3418a290418
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1376013
Greetz
DZG said:
http://www.google.com/support/forum...4f&hl=en&fid=1b777a366748b64f0004b3418a290418
Click to expand...
Click to collapse
Sorry don't have them
Bounced off a tower to a forum near you!
Perhaps the problem is with ota build. Most here are rooted with custom rom. Are you by chance running a custom rom or the stock one that was sent over the air?
Sent from my Nexus S 4G using xda premium
Bruce lee roy said:
Perhaps the problem is with ota build. Most here are rooted with custom rom. Are you by chance running a custom rom or the stock one that was sent over the air?
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
phone is default updated OTA
Then perhaps you can root and install a custom rom. It seems to me when I download a custom rom ota, its more likely to be corrupt. If its stock you want, it's available here. Better yet you might try Pete's Bugless Beast- stock with some additional enhancements. That way you get the stock a stock experience ... but better
Sent from my Nexus S 4G using xda premium
It was the other way round for me, I've only had the rebooting issue on my 9023 when I was using a couple of different cm roms, and it went away when I went back to stock. Have tried some other non cm roms, but not for long enough to show any effects.
No reboot, fortunately
That's an issue with 2.3.1, just update to 2.3.4 ota and it should be gone
Sent from my Nexus S using XDA App
scrapperstoo said:
It was the other way round for me, I've only had the rebooting issue on my 9023 when I was using a couple of different cm roms, and it went away when I went back to stock. Have tried some other non cm roms, but not for long enough to show any effects.
Click to expand...
Click to collapse
The CM reboots and sod are know bugs for CM and many have reported the problem stems from the flashing alternative kernel. I've been on GLADOS CFS @ 1.4 for several days now and have had absolutely no problems.
Sent from my Nexus S 4G using xda premium
I've never had any random reboots on my NS4G...nor have I even heard of this being an issue with the NS line, at all. I've been flashing new roms/kernels like crazy for the last 3 months I've been using this phone...the longets I think I've gone without a single flash is probably 4 days....and I've never had a single hardware issue of any kind These phones seem really rock-solid to me!!
They've turned a Samsung hater into a Samsung fan overnight!!! I'd buy a GN in a heartbeat if I hadn't JUST bought my NS4G lol
Just received Nexus 4 from US friends to here in India. I am getting constant reboots. They are very very frequent. Like once in every 10 minutes. Generally occurring when I make calls and into it 10 seconds. Seems like its hot reboot.
I received it in Android 4.2, which I immediately updated to 4.2.1, so I have no experience if it had the issue in 4.2.
I tried the following:
1) Factory Reset
2) Putting it back to Android 4.2
3) The latest nightly build of CM 10.1
The issue existed everywhere. I also have logcat constantly recorded before the reboots. Here is one of the instants:
http://pastebin.com/4JPW20xu
Any suggestions or advice? As of now I am planning to send it back to US for getting it replaced. But I want to try every possible solution in case it is a software issue..
Thanks in advance
Flash a custom kernel such as Franco. Kernel is what throttles your phone in temperatures etc.
Sent from my Nexus 4 using xda premium
Lemme try that, though CM 10.1 build kernel had the same issues.
Tried franco kernel. Still the same issue is there.
CPU Spy is not showing more times at higher frequency. Is temperature throttle possible?
zephiK said:
Flash a custom kernel such as Franco. Kernel is what throttles your phone in temperatures etc.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I doubt these are thermal reboots.. It is probably something wrong internally that is causing it. Bad eMMC maybe?
Sent from my Nexus 4 using Tapatalk 2
joshnichols189 said:
I doubt these are thermal reboots.. It is probably something wrong internally that is causing it. Bad eMMC maybe?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
So good thing will be to get it replaced I guess..
Sent from my GT-I9300 using xda premium
Hello, I got my nexus 4 three days ago and I'm facing a problem.
I can't seem to get realtime whatsapp notifications and when I go to the play store or YouTube my WiFi drops and it says connection time out retry and whatsapp messages take forever to receive. Is this a known bug in the nexus 4? Or should O replace my phone and get a new nexus with guarantee.
I'm currently using the march 18 Paranoid Android with Stock PA kernel, I'm not using any battery saver app (I'm using the same apps that I had on my S2) and none of them does anything to WiFi.
I flashed PA too fast after I got the phone but I think I was having this issue out of the box. I haven't changed DPI either.
Thanks in advance.
I tried changing kernel and nothing. Anyone? /:
There is a thread about it in general. But basically known bug, when on wifi and your phone screen is off (in deep sleep) you get delayed notifications or no notifications till you wake the device up.
In the android development section there is a kernel that fixes it for most (myself included.) on my phone and out so can't give links.
Sent from my Nexus 4 using xda app-developers app
I posted my problem in PA thread and no1 seems to be having that problem like me, shouldn't franco's kernel have this issue fixed? Is that the only kernel that fixes that
I agree that it seems odd more people aren't complaining about it. I only really noticed it when I tried to use voip and the phone wouldn't ring when the screen was off.
So far only the one kernel I told you about fixes it. However Google is aware and working on a fix so in time all kernels will be fixed
Sent from my Nexus 4 using xda app-developers app
Are the delayed notifications only a problem on wifi? What about when using HSPA+/3G?
Andie00 said:
Are the delayed notifications only a problem on wifi? What about when using HSPA+/3G?
Click to expand...
Click to collapse
wifi only
Andie00 said:
Are the delayed notifications only a problem on wifi? What about when using HSPA+/3G?
Click to expand...
Click to collapse
Wifi only ;/
Thank you.
So, I have my phone rooted running a modified version of CM10.2. Recently, my phone started going into a "sleep of death" while charging overnight, where the phone is still on but is nonresponsive, requiring me to reboot. So I downloaded Safe Charge and it helped... Kind of. Now instead of going SoD every night, it only does it sometimes.
So, is what I'm experiencing part of the infamous JSS ROM deadlocks I've been hearing about? And is there some way to fix this, or am I just going to have to deal with it until KitKat comes out?
Sent from my Nexus 4 using xda app-developers app
jspitzer221 said:
So, I have my phone rooted running a modified version of CM10.2. Recently, my phone started going into a "sleep of death" while charging overnight, where the phone is still on but is nonresponsive, requiring me to reboot. So I downloaded Safe Charge and it helped... Kind of. Now instead of going SoD every night, it only does it sometimes.
So, is what I'm experiencing part of the infamous JSS ROM deadlocks I've been hearing about? And is there some way to fix this, or am I just going to have to deal with it until KitKat comes out?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
flash stock, you wont have to deal with it.
jspitzer221 said:
So, I have my phone rooted running a modified version of CM10.2. Recently, my phone started going into a "sleep of death" while charging overnight, where the phone is still on but is nonresponsive, requiring me to reboot. So I downloaded Safe Charge and it helped... Kind of. Now instead of going SoD every night, it only does it sometimes.
So, is what I'm experiencing part of the infamous JSS ROM deadlocks I've been hearing about? And is there some way to fix this, or am I just going to have to deal with it until KitKat comes out?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
SoD seems to show up randomly... I've heard that JWR ROMs have less SoDs than JSS so you could try one, or if your not into switching ROMs here is an app (free) that could help you. It's called Safe Charge, and the comments say that it works great.
If you read my OP, I already have Safe Charge installed and am still getting sod. I really like the ROM I'm using, but I may just have to switch to avoid this unfortunate issue.
Sent from my Nexus 4 using xda app-developers app
jspitzer221 said:
If you read my OP, I already have Safe Charge installed and am still getting sod. I really like the ROM I'm using, but I may just have to switch to avoid this unfortunate issue.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Oops I guess I missed that part... I'm pretty sure that you can find a near similar ROM/kernel setup for JWR... If all else fails, try stock...
(Oh and if you can still RMA it, do it. People have speculated that its a hardware issue...)
No worries. I'm trying out SlimBean because I hear that doesn't have the issues, but not being able to use Franco with it is a bit of a bummer. In fact I haven't yet found a third party kernel that does work with it.
Sent from my Nexus 4 using xda app-developers app
I had this happen to me with a particular rom. Everything was great until id lock the phone, then try to unlock and see nothing but a black screen. I switched roms and it never happened again.
Sent from my SGH-I317M using xda premium
Hi all.
I've been looking at different threads and a few people talk about it but not seen any fixes.
When I receive a call I get a 3-4 second delay before the screen wakes up meaning I don't know who is call or able to answer the call.
I'm running PA4 with r201 FK
If any one knows a fix please share.
Sent from my Nexus 4 using Tapatalk
Even we are facing similar issue on Note 2. Tried few things but issue still persists.
Seemingly got something to do with some service.
So it's not device related then?
Sent from my Nexus 4 using Tapatalk
Was just using my phone and tookna call, even when screen was on it still took a long time to show who was calling!?!
Sent from my Nexus 4 using Tapatalk
Seems to be getting worse! I have to wait for about 5 seconds now, or maybe it already did.
Does no one have a fix?
Thinking about reverting to stock to see if that fix's it then maybe flash each thing one at a time and see when it breaks.
Sent from my Nexus 4 using Tapatalk
If you're playing around with kernel's and under clocking the CPU this can affect how quickly the phone wakes up. But my phone has a delay of a few seconds before I am am aware of a call coming in. Maybe it will be fixed in a future update.
Phone : Nexus 4 /Rom : cataclysm / Kernel : Stock.
I've only installed them the same as others but they don't seem to suffer the same problems.
Any one have any fixes?
Sent from my Nexus 4 using Tapatalk
foxguard said:
I've only installed them the same as others but they don't seem to suffer the same problems.
Any one have any fixes?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
same problem to me !!! i9100g cm11 last update!!!i hope they fix it!!
yohan7 said:
same problem to me !!! i9100g cm11 last update!!!i hope they fix it!!
Click to expand...
Click to collapse
Installed stock and all is fine, have unrooted my phone and now starting fresh to see if helps.... fingers crossed!
foxguard said:
Installed stock and all is fine, have unrooted my phone and now starting fresh to see if helps.... fingers crossed!
Click to expand...
Click to collapse
Aaaaaand what happend? Did you resolved problem? I have problem too on cataclysm and hells b43 kernel.
Deni_NS said:
Aaaaaand what happend? Did you resolved problem? I have problem too on cataclysm and hells b43 kernel.
Click to expand...
Click to collapse
I remember having this issue with franco r201 I think, but it went away when I updated the kernel/changed kernels
lopezk38 said:
I remember having this issue with franco r201 I think, but it went away when I updated the kernel/changed kernels
Click to expand...
Click to collapse
And now your kernel is?
Deni_NS said:
And now your kernel is?
Click to expand...
Click to collapse
It went away for me with franco r203 but I had to restore a nandroid running franco kernel + r200 and I haven't checked for the bug since
lopezk38 said:
It went away for me with franco r203 but I had to restore a nandroid running franco kernel + r200 and I haven't checked for the bug since
Click to expand...
Click to collapse
I'll try then r203. Thanks
I installed a different ROM with stock kernsl and had same prob.
Did a complete wipe and unroofed the phone, took back to stock and all was ok.
Rerooted the phone, installed PA, all fine. Installed r203 and still all good
Sent from my Nexus 4 using Tapatalk
foxguard said:
Hi all.
I've been looking at different threads and a few people talk about it but not seen any fixes.
When I receive a call I get a 3-4 second delay before the screen wakes up meaning I don't know who is call or able to answer the call.
I'm running PA4 with r201 FK
If any one knows a fix please share.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
If you have DU Battery Saver or any similar app which puts your device on low CPU usage upon locking, then uninstall it. It worked perfectly in my case.