Has the 4.4 update fixed random reboots for anyone? I am have not gotten the 4.4 OTA yet, but was hoping it may fix the reboots.
Right now I get a reboot even two days or so, mostly (not always) when the screen is off. I am pretty sure it's a software issue, at least for me.
Sent from my Nexus 7 using Tapatalk 4
cowisland said:
Has the 4.4 update fixed random reboots for anyone? I am have not gotten the 4.4 OTA yet, but was hoping it may fix the reboots.
Right now I get a reboot even two days or so, mostly (not always) when the screen is off. I am pretty sure it's a software issue, at least for me.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
I still get them with 4.4.
Thanks, there goes my hope...
Sent from my HTC6435LVW using Tapatalk
cowisland said:
Thanks, there goes my hope...
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
I had this issue... maybe 2 or 3 time / week
after upgrading to 4.4.... it happened, but only once in the last 2 weeks...
So i'm not sure if there is an improvement or not
Just got the OTA. Will report back in a couple of days.
After the second JB OTA I had no reboots, so I know it's possible! Overvolt baby overvolt...
Sent from my HTC6435LVW using Tapatalk
Reboots
I've had no reboots for a couple of weeks, when I don't install any unknown apps. As soon as I install a few unknown apps, I start getting 1-4 reboots per day. I've already tried flashing a fresh factory image and a ton of other things. I'm fairly certain that anyone with reboot problems should create bug reports and flood google with every single bug report until they fix it. In another six months, they'll probably say that they no longer officially support the device or something equally messed up.
support dot google dot com /nexus/contact/bugreport
I have my n7 for about a week and had no single reboot yet.
Running on 4.4 (ART).
Sent from my Nexus 7 using Tapatalk 4
Related
anyone possibly have a solution to the random reboots issue with these nightlys? also having a lot of trouble with bluetooth devices not connecting automatically. I have to go into the settings and connect manually. pretty annoying.
any help is greatly appreciated!!!
Good grief wrong thread
Sent from my SGH-I747 using xda app-developers app
For the reboots, are you on the jb bootloader? As for Bluetooth, try turning your bt device on, then turning on bt fir the phone
It's called nightly for a reason. They're unstable builds that gradually progress. If you can't handle the bugs, stick with the stable build.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
lilmeanz said:
Good grief wrong thread
its really annoying that people like you always post this dog **** rather than offer up a link to where this thread should go. how about a little less holiness and bit more constructiveness.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
mrhaley30705 said:
For the reboots, are you on the jb bootloader? As for Bluetooth, try turning your bt device on, then turning on bt fir the phone
Click to expand...
Click to collapse
no special bootloader. cm10.1. no special kernel either. whatever comes with the build is what im using. the bt used to work fine then this started happening.
Domoo said:
It's called nightly for a reason. They're unstable builds that gradually progress. If you can't handle the bugs, stick with the stable build.
i get that these are unstable..... how come then was it working just fine at one point then it all went to **** after updating with one of the rc's and/or nightlys? if they are supposed to get progressively better then how do you explain this??
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Nobody said that they get progressively better. They progress as they add new features or tweaks that tend to break other things. Fixing one problem may cause another to show up. If every build was to improve the rom, it would be stable in a month, but that's not how it works.
The bluetooth issue has been beat to death in the i747 cyanogenmod development thread. All you can do is wait till they fix the issue. Just flash back to a build with the bt working and follow the development thread. I'm sorry if this comes out in the wrong way.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
So I have installed fair share of Google edition Roms from probably 4 different developers and used several different kernels and what always happens is eventually the whole phone becomes saggy and slow and I have to reboot and it fixes it a little but then it comes back. This always happens it make take a couple days or couple weeks. Anyone else notice this or is it just me?
Sent from my GT-I9505G using Tapatalk 4
byron1985 said:
So I have installed fair share of Google edition Roms from probably 4 different developers and used several different kernels and what always happens is eventually the whole phone becomes saggy and slow and I have to reboot and it fixes it a little but then it comes back. This always happens it make take a couple days or couple weeks. Anyone else notice this or is it just me?
Sent from my GT-I9505G using Tapatalk 4
Click to expand...
Click to collapse
The Google Edition ROMs I've used, both 4.2.2 and 4.3 have always been very snappy; although 4.2.2 is the only version I've never experienced any sort of problem with. It runs and runs like a champ... 4.3 though, after about a day or so starts rebooting on its own, doing a black screen of death, etc... Nothing like that with 4.2 though.
It could be because of certain apps that you're installing, since you said it happened throughout 4 different ROM's.
byron1985 said:
So I have installed fair share of Google edition Roms from probably 4 different developers and used several different kernels and what always happens is eventually the whole phone becomes saggy and slow and I have to reboot and it fixes it a little but then it comes back. This always happens it make take a couple days or couple weeks. Anyone else notice this or is it just me?
Sent from my GT-I9505G using Tapatalk 4
Click to expand...
Click to collapse
Nope. It happened to me on every version I tried. I'm back on stock and I am happy knowing my phone will perform when it needs to.
Sent from my SGH-M919 using Tapatalk 4
My 16GB flo was working fine from the beginning. Always kept it up to date with android releases. Never had an issue. Just today while swyping noticed some weird behavior.So, I tested with a multi touch tester. There were some fake touches recorded. It didn't even allow me to reboot. Later with some effort I managed though. After reboot, it works fine. I'm scared cause I bought that in US and I doubt the so called international warranty will be honored in India.Has this occurred to anyone else? What shall I do if it happens again? Is there some fix for this?
littleromeo said:
My 16GB flo was working fine from the beginning. Always kept it up to date with android releases. Never had an issue. Just today while swyping noticed some weird behavior.So, I tested with a multi touch tester. There were some fake touches recorded. It didn't even allow me to reboot. Later with some effort I managed though. After reboot, it works fine. I'm scared cause I bought that in US and I doubt the so called international warranty will be honored in India.Has this occurred to anyone else? What shall I do if it happens again? Is there some fix for this?
Click to expand...
Click to collapse
I had the same experience the other day. Currently running
Latest version of Clean Rom with ElementalX kernel. After I was finally able to reboot, all was well.
Sent from my Nexus 7 using Tapatalk
dantegl36 said:
I had the same experience the other day. Currently running
Latest version of Clean Rom with ElementalX kernel. After I was finally able to reboot, all was well.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I'm running stock+xposed.
Testing with multi touch app seemed to have made it worse for me, even prevented me shutting it down. Hope it doesn't come back.
littleromeo said:
My 16GB flo was working fine from the beginning. Always kept it up to date with android releases. Never had an issue. Just today while swyping noticed some weird behavior.So, I tested with a multi touch tester. There were some fake touches recorded. It didn't even allow me to reboot. Later with some effort I managed though. After reboot, it works fine. I'm scared cause I bought that in US and I doubt the so called international warranty will be honored in India.Has this occurred to anyone else? What shall I do if it happens again? Is there some fix for this?
Click to expand...
Click to collapse
Take a look at this thread, I had the same problem and after flashing boot-ts10.IMG it was fixed.
The flash persists between any new ROM flashing
Sent from my Nexus 7 using XDA Premium 4 mobile app
Abel669 said:
Take a look at this thread, I had the same problem and after flashing boot-ts10.IMG it was fixed.
The flash persists between any new ROM flashing
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If an RMA is not an option, try Abel's solution. It boils down to bad hardware and no quality control. I had to RMA my first one for the exact same reason. Second one is fine.
If you do some googling, you will see that thousands of people have had this problem. Any definitive word from Google or Asus? You wish. They will never admit they made a mistake.
littleromeo said:
I'm running stock+xposed.
Testing with multi touch app seemed to have made it worse for me, even prevented me shutting it down. Hope it doesn't come back.
Click to expand...
Click to collapse
Abel669 said:
Take a look at this thread, I had the same problem and after flashing boot-ts10.IMG it was fixed.
The flash persists between any new ROM flashing
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks, will do if it starts again.
Abel669 said:
Take a look at this thread, I had the same problem and after flashing boot-ts10.IMG it was fixed.
The flash persists between any new ROM flashing
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Aerowinder said:
If an RMA is not an option, try Abel's solution. It boils down to bad hardware and no quality control. I had to RMA my first one for the exact same reason. Second one is fine.
If you do some googling, you will see that thousands of people have had this problem. Any definitive word from Google or Asus? You wish. They will never admit they made a mistake.
Click to expand...
Click to collapse
Yes I read about them but this is weird cause a reboot solved the problem.
Had this issue start yesterday. Running Sinless 3.2.2 on stock kernel. I've noticed it only start since installing Xposed but that could be coincidence. Reboot fixed it but woke up to it again today...
Sent from my Nexus 7 using xda app-developers app
mister2quick said:
Had this issue start yesterday. Running Sinless 3.2.2 on stock kernel. I've noticed it only start since installing Xposed but that could be coincidence. Reboot fixed it but woke up to it again today...
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
The one I had (before I sent it back to Google), would only do it after it had been started for a while. Reboot would make it go away for a while, but it always came back.
Not related to Xposed.
Just wanting to know how good is the m5 CM11 (the latest one on cyanogenmods website) battery life is.
And if art would be supported,
Sorry for stupid questions, thanks in advance c;
Sent from my Nexus 7 using xda app-developers app
In my opinion most Roms have close to the same battery life
But with CM its better than stock battery life.
ART is supported
No question is stupid
Sent from my Nexus 7 using xda premium
is anyone using a CM11 version that does NOT randomly reboot at times? Any N7 2013 I install it on will reboot 1 or more times a day just sitting there. Load reboot logger or something to see, you may not catch it doing it.
My deb N7 on CM 11 Nightlies never reboot rendomly, or i've never see it
jmdearras said:
is anyone using a CM11 version that does NOT randomly reboot at times? Any N7 2013 I install it on will reboot 1 or more times a day just sitting there. Load reboot logger or something to see, you may not catch it doing it.
Click to expand...
Click to collapse
Random rebooting is a general 4.4.2 problem
Wait for the upcoming 4.4.3 update, nothing else you can do
rap3rman said:
Random rebooting is a general 4.4.2 problem
Wait for the upcoming 4.4.3 update, nothing else you can do
Click to expand...
Click to collapse
I strongly disagree. Stock is solid as a rock as are most other roms, with the exception of CM11 and Omni.
It's a code issue. i bought a second N7 because someone convinced me it was my hardware, and it rebooted in the 1st 3 hours on CM11
Jim
I'm not experiencing random reboots, even with the latest Nightlies.
I was on cm11 for like a week with no reboots. Battery life was OK. On aokp for a change now.
Sent from my Nexus 7 using Tapatalk
What about slimkat?
Is that rom pretty stable?
sent from my LG Optimus L9 P769 v20h
I'm on YouTube (aSuperSaiyanG0D)
Maybe i will test slimkat soon, this ROM sounds great
vparres said:
I'm not experiencing random reboots, even with the latest Nightlies.
Click to expand...
Click to collapse
I did not notice the reboots until I left it connected to a bluetooth speaker that chimes when connected. Then I loaded reboot logger, and was amazed how often it was rebooting.
I've checked reboot logger and i definitely dont see any reboot
Ok Verizon had a update a couple days ago I'm fine but my wife's galaxy note 4 is not making it threw a whole day and she's not even on it much I've seen there where other people having issues once update hit there phone... 1. From experience I know you can't usually due this but is there anyway to backtrack and install an older version of Android.. 2. Is there a way to reinstall the update to see if it was a bad install or file I'm not sure what is going on but trying to figure this out she is running on super power saving mod to survive the day I'd say battery issue but the day the update hit this issue started... Any advice much appreciated if any thank you
Sent from my SM-N910V using XDA Premium HD app
Forgot to mention factory reset did not fix this issue
Sent from my SM-N910V using XDA Premium HD app
jprocket45 said:
Ok Verizon had a update a couple days ago I'm fine but my wife's galaxy note 4 is not making it threw a whole day and she's not even on it much I've seen there where other people having issues once update hit there phone... 1. From experience I know you can't usually due this but is there anyway to backtrack and install an older version of Android.. 2. Is there a way to reinstall the update to see if it was a bad install or file I'm not sure what is going on but trying to figure this out she is running on super power saving mod to survive the day I'd say battery issue but the day the update hit this issue started... Any advice much appreciated if any thank you
Sent from my SM-N910V using XDA Premium HD app
Click to expand...
Click to collapse
Try flashing the full tar using Odin from here. You can go with the original or the newer version. I haven't had a battery issue with mine on either update but that all depends on the usage.