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
Related
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
My Nexus 7 which is running on SmoothROM 4.1 and the M-Kernel, is freezing regulary since last week. I didnt install or mos anything, so i wpnder why it crashed. It isnt OC`d. I dont know how I can upload logs, just say it It freezes the screen and reboots after 3 secs.
Sent from my Nexus 7 using XDA Premium HD app
Leonelf said:
My Nexus 7 which is running on SmoothROM 4.1 and the M-Kernel, is freezing regulary since last week. I didnt install or mos anything, so i wpnder why it crashed. It isnt OC`d. I dont know how I can upload logs, just say it It freezes the screen and reboots after 3 secs.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Well, without any sort of kernel log/logcat of any type, it's anyone's guess...
Reflash the ROM only and run that for a couple of days before flashing another kernel, or try another ROM altogether.
Hm, can u say to ms, how i can make a log?
Sent from my Nexus 7 using XDA Premium HD app
Leonelf said:
Hm, can u say to ms, how i can make a log?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
You'll probably want to pull a dmesg log and/or kmsg log, I've never done that but here's how you can pull that info: http://forum.xda-developers.com/showthread.php?t=1520508
At that point, if you get these, you'll want to send them to the ROM and kernel developers of the ROM/kernel you're using to see what they see in those outputs.
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
Hey so I've been running aokp for a few days now, and suddenly I noticed that the sound isn't working, not for notifications, not for music, videos, anything. Not even when the headset is plugged in. So I flashed my stock Rom backup and it still isn't working, any ideas?? Thanks!
Sent from my Nexus 4 using xda app-developers app
Ok this is weird, sound just started working on my stock Rom. Haven't tried aokp yet, the restore backup of stock Rom took 30 minutes and I need to sleep soon so I don't want to risk hanging to stay awake for it, it normally takes 3 minutes to restore backups though, idk what's wrong
Sent from my Nexus 4 using xda app-developers app
Melad360 said:
Ok this is weird, sound just started working on my stock Rom. Haven't tried aokp yet, the restore backup of stock Rom took 30 minutes and I need to sleep soon so I don't want to risk hanging to stay awake for it, it normally takes 3 minutes to restore backups though, idk what's wrong
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Did you happen to flash that build posted by the random user?
Sent from my Nexus 4 using xda premium
No, I searched on the internet for the newest version of aokp and used that one
Sent from my Nexus 4 using xda app-developers app
I had this problem but the latest roman nightly is fine
Sent from my Nexus 4 using Tapatalk 2
What is the Roman nightly? Another version? Sorry I'm a noob at the Rom business lol I just got into it
Sent from my Nexus 4 using xda app-developers app
Melad360 said:
Hey so I've been running aokp for a few days now, and suddenly I noticed that the sound isn't working, not for notifications, not for music, videos, anything. Not even when the headset is plugged in. So I flashed my stock Rom backup and it still isn't working, any ideas?? Thanks!
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I'm having a pretty same problem here, the only difference is that I'm running Paranoid Android on my Nexus 4. Do you find any solution yet?
Hey guys, I'm wondering if anyone knows a setting in the latest kernel (008-tbm) that affects wireless charging. I am on stock ROM with only this kernel installed. Wireless charging worked fine until I installed this kernel, so I know something is goofed up with my kernel settings. I'm UV -12.5 mV global
Sent from my Nexus 4 using xda app-developers app
freefromapple said:
Hey guys, I'm wondering if anyone knows a setting in the latest kernel (008-tbm) that affects wireless charging. I am on stock ROM with only this kernel installed. Wireless charging worked fine until I installed this kernel, so I know something is goofed up with my kernel settings. I'm UV -12.5 mV global
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Why the hell are you asking this in nexus 4 GENERAL? When there is a thread for this kernel in Original development.. Sigh
Sent from my Nexus 4 using xda premium
Girn said:
Why the hell are you asking this in nexus 4 GENERAL? When there is a thread for this kernel in Original development.. Sigh
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
he doesnt have enough posts to post in the development sections.
Thank you for clearing that up for him. I hate posting stuff because everyone has to be an @$$ about helping out. If you don't want to help just move on, I don't want to hear how stupid I am just what I can do that I haven't thought of. Thanks
Sent from my Nexus 4 using xda app-developers app
I'm on his 008tbu and have no issues with wireless charging.
Sent from my Nexus 4 using Tapatalk 2
freefromapple said:
Thank you for clearing that up for him. I hate posting stuff because everyone has to be an @$$ about helping out. If you don't want to help just move on, I don't want to hear how stupid I am just what I can do that I haven't thought of. Thanks
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
try raising your voltages, undervolting can have create such issues. every device is different in what it likes and dislikes.
OK thanks for the help guys. I'll try that right away. Right now it'll show as charging for about five minutes and then for some reason will stop.
Sent from my Nexus 4 using xda app-developers app
OK I tried that and it didn't work, I'm using the intellidemand governor and all of the rest of faux123's recommended settings. My CPU bin is nominal if that helps any.
Sent from my Nexus 4 using xda app-developers app
Here's a screenshot of my battery graph.
Sent from my Nexus 4 using xda app-developers app
Girn said:
Why the hell are you asking this in nexus 4 GENERAL? When there is a thread for this kernel in Original development.. Sigh
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Why do you even care? It mean that much to you?
Posts like yours are more annoying than the original threads.
Sent from my Nexus 4 using xda premium
you should try a different kernel, just to make sure. it takes seconds to flash a kernel, so that shouldnt be an issue. if it works fine with another kernel, then the issue is the kernel. if the same issue persists, then its your rom or device.
Girn said:
Why the hell are you asking this in nexus 4 GENERAL? When there is a thread for this kernel in Original development.. Sigh
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Posts like this make me believe that Reddit & Rootwiki users are right, about the attitude of many XDA users..
Turbotab said:
Posts like this make me believe that Reddit & Rootwiki users are right, about the attitude of many XDA users..
Click to expand...
Click to collapse
unfortunately, many reddit and rootwiki users arent any better.
Yeah I'm on faux's kernel as well with no wireless charging problems. There's a good chance that it might be stopping because your battery is getting too hot. Do you have daydream enabled? Does your phone feel hot when charging?
Sent from my Nexus 4 using Tapatalk 2
Yeah I just got it working for about 30 minutes and my phone is super hot. It's never been this hot before so I'm gonna try a new kernel and see what happens like someone said earlier to narrow it down if it's the kernel for sure
Sent from my Nexus 4 using xda app-developers app
What charger are you using? Some do not work well with the N4.
I have used several different kernels and none have affected the wireless charging. My phone gets up to 41°C while charging wirelessly so getting hot is not unusual.
I'm using the official nexus charging orb from Google play. I just flashed a new kernel and wireless charging seems to be back working. I'm gonna give it another hour just to make sure before I make any assumptions
Sent from my Nexus 4 using xda app-developers app
One weird thing I did notice though is that on faux kernel I could not UV past -50mV without my phone rebooting, making my lowest clock of 384Mhz at 850mV. However I'm on harsh kernel right now and it shows that my lowest clock is at 800mV stock without any adjustments and is working fine. Would that make any sense? I know the governors could possibly be more or less harsh on the battery but shouldn't the failure value resulting in rebooting be the same no matter what governor or kernel you use? I'm by no means an expert as to why I'm asking
Sent from my Nexus 4 using xda app-developers app
Is not unheard of to not be stable at the same voltages with different kernels. Also if you were using one of the kernels with turbo boost your chip may have needed a higher voltage for the higher frequencies. Or not, I don't know lol.
Glad your charger is working now. I like Harshes kernel.