Related
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
More often than not, I notice when I attempt to unlock my nexus 7 (inputting the correct lock pattern) it will freeze on the inputted pattern and become not responsive. I have to hold down the power button until it reboots. Can anyone help me out with this? I am running the newest nexus 7 paranoid android along with the motley kernel.
Sent from my Nexus 4 using xda app-developers app
tsmith9191 said:
More often than not, I notice when I attempt to unlock my nexus 7 (inputting the correct lock pattern) it will freeze on the inputted pattern and become not responsive. I have to hold down the power button until it reboots. Can anyone help me out with this? I am running the newest nexus 7 paranoid android along with the motley kernel.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Paranoid Android can be a bit slow at times, but that seems a bit unnatural. I would do a wipe and reinstall. See if that fixes the problem.
I actually flashed back to the March 23 build. Hasn't done it since thank god.
Like this?
http://www.youtube.com/watch?v=4sGNwF_G16s
Mine was and at first I blamed the case. But it does it with every case. So i was thinking of returning it. But then I got this email from Poetic(i had slammed them on Amazon with a one star rating). It said:
We would also like to inform you that if you face any issue regarding wake up function mostly when you open the case we request you to please check your WIFI Connection (to make sure you are successfully connected to WIFI). If your WIFI connection is disabled or not connected to WIFI Successfully, then your device won’t wake up all the times. This is not the issue of the case itself.
Click to expand...
Click to collapse
I tried turning my WIFI on and connecting, but it did not help. Then I tried with it off. Same problem. Now I am thinking I really need to return this thing, only to find out my friends does the same exact thing. So what the hell? Are they all doing this? Most? Only a few? I really do not want to return if all of them are gonna do it, and it would seem a software issue in that case. But if mines got hardware problems I really should return it.
My case has been working fine.
Sent from my Galaxy Nexus
Landara said:
Like this?
http://www.youtube.com/watch?v=4sGNwF_G16s
Mine was and at first I blamed the case. But it does it with every case. So i was thinking of returning it. But then I got this email from Poetic(i had slammed them on Amazon with a one star rating). It said:
I tried turning my WIFI on and connecting, but it did not help. Then I tried with it off. Same problem. Now I am thinking I really need to return this thing, only to find out my friends does the same exact thing. So what the hell? Are they all doing this? Most? Only a few? I really do not want to return if all of them are gonna do it, and it would seem a software issue in that case. But if mines got hardware problems I really should return it.
Click to expand...
Click to collapse
Hate to say it but if you are on stock, I think the device crashes and does not power on with the cover anymore. I had that issue when I was on stock.
I've since moved to CM10.2 nightlies and the cover turns on the device every single time. No issues here.
Also, with CM10.2, no more random reboots. You owe it to yourself to get off of stock.
There definitely is an issue with having wifi on and no access point around w/r/t magnetic on
I've seen this on a couple of units
Here are the symptoms with my cover:
* It never fails to put my tab to sleep.
* With wifi off, it rarely wakes up my tab. With wifi on, it wakes up the tab quite often... unless the Tab went to a deep sleep.
* When plugged in (PC or charger), it works beautifully, wifi on or off.
So it's hard to point the finger to Poetic.
There are plenty of people who don't have any issue.
I have replacement coming from the Amazon seller, so will see.
Open your case and WAIT...
so far mine always turns on... BUT it may be delayed by 10-15 seconds.
(by that time most of us have closed/re-opened the case a few times).
Mine works like a charm, I cycle through every Locket ad in like 30 seconds using my cover lol
Mine fails perhaps 20% of the time. It can't be a cover issue though, because the cover is constant.
Just tested my Moko ultra slim case on CM kanged and it turns on and off like a champ. Quick and no delay. No reboots either. So for me it was a software issue.
For you, flash CM and see if it is. If you still have the problem on CM then exchange it.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Mine works fine with CM10.2 as long as WiFi is always on. If WiFi is set to turn off when sleeping it will not turn on after 15-20 minutes.
Sent from my Nexus 7 using xda premium
I posted about this same issue here: http://forum.xda-developers.com/showthread.php?p=44926734
Sometimes it will wake up after a delay (20-30 seconds) and sometimes it will just sit there until I press the power button. My first gen N7 never had this problem. I really don't want to let my WiFi run 24/7 just so my tablet will wake up.
Sent from my ADR6425LVW using xda app-developers app
RKight said:
I posted about this same issue here: http://forum.xda-developers.com/showthread.php?p=44926734
Sometimes it will wake up after a delay (20-30 seconds) and sometimes it will just sit there until I press the power button. My first gen N7 never had this problem. I really don't want to let my WiFi run 24/7 just so my tablet will wake up.
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
I have mine set to always on so it is ready through out the day and I manually turn WiFi out at night.
Sent from my Nexus 7 using xda premium
ncguy68 said:
I have mine set to always on so it is ready through out the day and I manually turn WiFi out at night.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
What's your battery life like, though? With light use, I can go a few days between charges.
Sent from my Nexus 7 using xda app-developers app
RKight said:
What's your battery life like, though? With light use, I can go a few days between charges.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
WiFi seems to use very little power. I average about 10 hours of screen on time per charge.
Sent from my Nexus 7 using xda premium
I'm using the MoKo case and do not have any problems with the case not waking the device when opened. I must say though I did not purchase the case for this feature. The case construction is good, it fits the device perfectly and looks.well in place, and provides protection for the screen. For those reasons I am satisfied with it.
Just got a poetic replacement case, no improvement.
But (at this point) I think it's a tablet issue. If google knows they will fix it later, just like some people having multi-touch issue.
Even with my WiFi off, on CM, its perfect. Tested with WiFi off, even waited like 5 minutes and tested again with no issues. Probably a rom issue. Is this on stock with the latest version?
Sent from my Nexus 7 using XDA Premium 4 mobile app
player911 said:
Even with my WiFi off, on CM, its perfect. Tested with WiFi off, even waited like 5 minutes and tested again with no issues. Probably a rom issue. Is this on stock with the latest version?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Mine is stock rooted, latest version, with a Moko case. If it sits idle for more than a few minutes, it will rarely turn on when the cover is opened. With short idle times, it will wake consistently. I may try CM eventually but, for now, I think I may just flash the Bulletproof kernel and enable the double tap to wake feature.
Sent from my Nexus 7 using xda app-developers app
For anyone having this issue, I found a thread on the Google product forums about this. That's apparently how they became aware of the other issues that have been reported. If you could, please post your problem in this thread: http://productforums.google.com/forum/m/#!category-topic/mobile/android-devices/8MTpqfFmw8Q
Sent from my Nexus 7 using xda app-developers app
zim2dive said:
Open your case and WAIT...
so far mine always turns on... BUT it may be delayed by 10-15 seconds.
(by that time most of us have closed/re-opened the case a few times).
Click to expand...
Click to collapse
Hahahahaha 10-15 seconds. STOP acting like that's NORMAL.
Sent from my Nexus 7 using XDA Premium 4 mobile app
hey guys, so im porting lg og 4.1.2 stock rom to nexus 4. already fixed kernel and got it booting. fixed audio touch and some random reboots and hw crash. also implemented soft keys.however its still pretty buggy(im fixing) as
camera dont work
screen shot dont work
sdcard dont work(/data works)
still some random reboots after wake the device
wifi dosent work
nfc dosent work
bt dosent work
data(cals,2g,3g,4g) all dosent work
so i wanna know if you guys want me to share to try or idk.
You probably can't do it, since all of the drivers and such are for 4.2 onwards.
Sent from my Nexus 4 using XDA Premium 4 mobile app
korockinout13 said:
You probably can't do it, since all of the drivers and such are for 4.2 onwards.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
actually just the 3g/2g/4g is only for the 4.2 for others i can use the lgog ones...
Hi,
Ive just bought a brand new Nexus 10 and its doing really wierd things.
After updating to Android 4.4.4 i kept getting kicked off and the device would go to the lock screen. Additionally the screen would do strange things when running Chrome like going totally black with a white ring in the center of the screen.
Also text doesnt seem to display properly at times; i have now downgraded back to version 4.2 which seems to have got some stability back howver text is still broken on occassion.... See attached.
Its really odd as i have a Nexus 7 mkII which ultra stable.
Could this be hw related or simply is the rom simply this buggy?
Thanks for any ideas.
Sent from my Nexus 10 using XDA Free mobile app
Ok so I updated to 4.3 and the machine seems to be stable minus the occasional logout when opening Chrome.... However text still has problems displaying; also as with Android 4.2 it seems the wifi kept disconnecting every few minutes. Since the AP being used was the spare wifi card in my Linux HTPC it migt have something to do with the Intel Centrino card at the other end. I have a spare 3com AP which I will try and if not I also have a spare Cisco wireless router which I can also hookup.....
Other then that I dont know???
Sent from my Nexus 10 using XDA Free mobile app
JohnnySSH said:
Ok so I updated to 4.3 and the machine seems to be stable minus the occasional logout when opening Chrome.... However text still has problems displaying; also as with Android 4.2 it seems the wifi kept disconnecting every few minutes. Since the AP being used was the spare wifi card in my Linux HTPC it migt have something to do with the Intel Centrino card at the other end. I have a spare 3com AP which I will try and if not I also have a spare Cisco wireless router which I can also hookup.....
Other then that I dont know???
Sent from my Nexus 10 using XDA Free mobile app
Click to expand...
Click to collapse
Have you tried a complete wipe (flashing the factory image and doing a data wipe/factory reset afterwards)? Not sure if that's what you did when you downgraded. I would think a 100% fresh start would help.
Yep I did... Sorry if wasnt clear. I even reformatted the partitions.....
I think what bothers me the most is the incomplete text...... When downgrading I got the stock rom from Google directly.
Also something funky is the screen seems to slightly flicker when running the Plex app. This could just be an app thing though as everything else is fine.
Sent from my Nexus 10 using XDA Free mobile app
JohnnySSH said:
Yep I did... Sorry if wasnt clear. I even reformatted the partitions.....
I think what bothers me the most is the incomplete text...... When downgrading I got the stock rom from Google directly.
Also something funky is the screen seems to slightly flicker when running the Plex app. This could just be an app thing though as everything else is fine.
Sent from my Nexus 10 using XDA Free mobile app
Click to expand...
Click to collapse
Boy. This is a real head scratcher. I've never heard of this before. It would be one thing if the screen was static, which would usually indicate a loose ribbon connection. Since you've already successfully flashed the factory image, I don't think it would be software related. But I can't think of any hardware issue that would cause this either.
Sent from my Nexus 10 using Tapatalk
Ok good news.... Using my spare Cisco wireless router I got stability on the wifi
I'm just thinking that maybe the issue could be something to do with the graphics chip??
Of course if I dont need to i really dont want to but if it isnt a software bug and the issue is hw related perhaps I should just contact the place where I bought it and get it replaced???
Sent from my Nexus 10 using XDA Free mobile app
JohnnySSH said:
Ok good news.... Using my spare Cisco wireless router I got stability on the wifi
I'm just thinking that maybe the issue could be something to do with the graphics chip??
Of course if I dont need to i really dont want to but if it isnt a software bug and the issue is hw related perhaps I should just contact the place where I bought it and get it replaced???
Sent from my Nexus 10 using XDA Free mobile app
Click to expand...
Click to collapse
Hi,
It is really bugging me, quite a weird issue. I believe it can be surely a defective unit, after all you flashed a stock ROM wiping completely and problems still persists.
I recommend you contacting the place you bought it. Hope you can get a replacement .
~Lord
"Dream On! Dream Until Your Dreams Come True!" - Dream On (Aerosmith)
Sent from my GT-I9505
Yeah I guess replacement is only way forward at this time
Sent from my Nexus 10 using XDA Free mobile app