Idk if its the ROM or the kernel. I'm running cna 3.6.6 and francos r23 and the tablet will turn off after awhile of inactivity. Sounds like a feature that can be turned off but figured I would ask here instead of spamming each thread before finding an answer lol.
Sent from my Galaxy Nexus using xda app-developers app
Do you have to turn it on while holding the power and vol down, then boot from, boot loader? If so its a sleep of death. Not supposed to happen but it does on some kernels at certain settings.
Sent from my Nexus 7
I had the same issue.... was running paranoid and alpha der kernel. I flashed the EOS ROM and faux kernel and all is right again.
Sent from my SPH-L710 using xda app-developers app
Same here.. belive it was with CM + franco r23.
SmoothROM with Bricked no problem.
Its a kernel/ROM thing i guess.
Sent from my Nexus 7 using xda app-developers app
Got the same issue with Stock 4.1.2 + Trinity Kernel.
On Glazed JellyBean v2 + Trinity Kernel it stoped.
My stock rooted N7 did it two or three times. Got it exchanged and had no trouble since.
Just a little thought, decided also to encrypt the tablet, just in case it turned off and wouldn't turn on again, and I had to return it in that state, without being able to do a factory reset and lose any sensitive data.
Phil
I guess some kernel settings just resulted in too deep of a sleep from nexus to wake from. Odd it happened on a couple different ones though.
Sent from my SPH-L710 using xda app-developers app
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
Any avid flashers go back to stock ROM and stay there? I flip flop between CM and aospa frequently and I'm considering going back to stock. Id think that Google optimised the stock ROM for the Nexus 4. Any comments. Ive always used custom roms
Sent from my Nexus 4 using xda premium
I haven't stayed there on the N4, my GN lived on stock for the last couple of months I used it.
That said if CM didn't exist I would have ZERO issues with rocking the stock images. I'd just carefully choose which market apps to fill some of the functionality void.
Sent from my Nexus 4 using Tapatalk 2
When I first got my n4 in November I immediately started flashing ROMs (cm being ROM of choice). But after about a month I went back to 100% stock unrooted and stayed that way. Its nice to know everything will just work, plus after a while I get sick of flashing ROMs all the time. Only thing about stock is it gets kinda boring after a while, which is why I flashed PA yesterday but I'm kinda already thinking about going back to stock lol... Nothing matches its speed & smoothness imo
Sent from my Nexus 4 using xda app-developers app
How bout battery life? I don't like using custom kernels... To many things to tinker with.
Sent from my Nexus 4 using xda premium
I wouldn't consider myself an avid flasher but I did try a ROM (AOKP) and ended up going back to stock because I like knowing everything will work on my phone when I need it to. On previous non nexus devices I always flashed ROMs that were as close to AOSP as possible because I think it's smoother (but they'd always have minor issues here and there were functionality didn't quite work all the way). I usually pick a ROM and stick with it. In this particular case I think it will be stock.
Sent from my Nexus 4 using xda app-developers app
Smallsmx3 said:
How bout battery life? I don't like using custom kernels... To many things to tinker with.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Same here, never been a huge fan of kernels. But I decided to give Franco a try and I can safely say battery is slightly better than stock. I was getting about 15 hrs + 3screen on with stock, now on PA w/ Franco I'm getting 4hrs screen on time. Only thing I noticed is every once in a while I see a tiny micro-stutter in an animation, but its worth it for an extra hr of SOT lol. Btw I'm running all stock settings on franco
Sent from my Nexus 4 using xda app-developers app
Anyone else getting the sleep of death with this ROM and kernel combo?
Sent from my Nexus 4 using xda premium
I get sod with harsh kernel too, ever since it changed to 4.2.2. It happens every time the screen goes off for a minute when not on charger. I never get sod with any other kernel.... shrugs
Yep same here been happening here all morning since I installed it. Pushing the eject button on this one
Sent from my Nexus 4 using xda premium
Never happened to me
Tapalked with a Nexusâ´
Maybe your voltages are too low? Or maybe try a different governor/scheduler combo such as Ondemand and CFQ or ROW or something. Still, I'm not sure ...
Switched to orca......loving it
Sent from my Nexus 4 using xda premium
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
My nexus 10 is randomly turned off, was using sentinelROM and now purity. Kernel is always the kernel from the rom. Any thought? Thanks
saryu said:
My nexus 10 is randomly turned off, was using sentinelROM and now purity. Kernel is always the kernel from the rom. Any thought? Thanks
Click to expand...
Click to collapse
Logcat would help. Theres always someone who can read them. Probably plenty of guides on how to read them too.
Sent from my Galaxy Nexus using XDA Premium HD app