My 7 qhd get the tint when warm and overheats by the back camera during heavy use, and now the screen has stops responding to touch when it gets too hot, but returns to normal after it cools down, anyone else have this issue?
Sent from my X9077 using XDA Premium 4 mobile app
was considering buying this device, but all the issues reported made me turn to LG G3. it's actually cheaper here than the find 7
Sent from my Nexus 5 using Tapatalk
bobbydigital222 said:
My 7 qhd get the tint when warm and overheats by the back camera during heavy use, and now the screen has stops responding yo touchs when it gets too hot, but returns to normal after it cools down, anyone else have this issue?
Sent from my X9077 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have the same Oppo Find 7 Premium X9077 but no problem. Everything ist running so smoothly
bobbydigital222 said:
My 7 qhd get the tint when warm and overheats by the back camera during heavy use, and now the screen has stops responding to touch when it gets too hot, but returns to normal after it cools down, anyone else have this issue?
Sent from my X9077 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I thought I was the only one. My touch becomes unresponsive when the screen heats up to a certain point. I have to turn off the screen and wait a few secs and turn it on again for me to be able to use it again.
coremark said:
I thought I was the only one. My touch becomes unresponsive when the screen heats up to a certain point. I have to turn off the screen and wait a few secs and turn it on again for me to be able to use it again.
Click to expand...
Click to collapse
Yup exact same problem here, I hope it's a software not hardware issue
Yes, I've had this exact problem a few times now. What did you guys do, return the phone?
I haven't experience this just yet, what ROMs are you guys running or programs which seem to cause this (Probably just intensive applications)
floxrin said:
was considering buying this device, but all the issues reported made me turn to LG G3. it's actually cheaper here than the find 7
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I considered the LG G3 but bought the Find 7 so I could use custom roms and customization without a lot of issues. Very happy with the Find 7 so far. When the new GPE or Android Silver product hits the shelf, might get that as well. How odd if there is a GPE or Android Silver version of the Find 7.
bobbydigital222 said:
My 7 qhd get the tint when warm and overheats by the back camera during heavy use, and now the screen has stops responding to touch when it gets too hot, but returns to normal after it cools down, anyone else have this issue?
Sent from my X9077 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
me too
same problem
i think i will return the phone for an replacement
Me too same Problem
Normaly the first upper 5mm of screen responds and the bottom 50mm responds. The Rest of the Screen does not work for me too. Then after shutting off and then boot up the whole screen reacts. On reboot it keeps on ignoring. But this comes first with the software update when i think of it. not the last, but that beforce.
???
bobbydigital222 said:
My 7 qhd get the tint when warm and overheats by the back camera during heavy use, and now the screen has stops responding to touch when it gets too hot, but returns to normal after it cools down, anyone else have this issue?
Sent from my X9077 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
What ROM are you using?
any special Kernel settings?
need more info than just saying bad things about it, i have the Find 7 QHD and Find 7a both running PA ROM with unified partition Layout and none of them is presenting these issues,
Note: i do use the find 7 as my Daily driver with heavy usage and i have no problems at all.!
rroohh93 said:
What ROM are you using?
any special Kernel settings?
need more info than just saying bad things about it, i have the Find 7 QHD and Find 7a both running PA ROM with unified partition Layout and none of them is presenting these issues,
Note: i do use the find 7 as my Daily driver with heavy usage and i have no problems at all.!
Click to expand...
Click to collapse
I'm on gummy rom no kernel tweaks
Try playing a game like xcom or galaxy on fire then you'll see what I mean
bobbydigital222 said:
I'm on gummy rom no kernel tweaks
Try playing a game like xcom or galaxy on fire then you'll see what I mean
Click to expand...
Click to collapse
Just played galaxy on fire and no problems at all.
Im on PA Rom 4.5 beta 1 and franco's kernel.
Has been fixed in the latest update
jackdh said:
I haven't experience this just yet, what ROMs are you guys running or programs which seem to cause this (Probably just intensive applications)
Click to expand...
Click to collapse
I haven't experienced any problems like this either with 7a or 7s.
rroohh93 said:
Just played galaxy on fire and no problems at all.
Im on PA Rom 4.5 beta 1 and franco's kernel.
Click to expand...
Click to collapse
Where did you get franco's kernel?
bobbydigital222 said:
Where did you get franco's kernel?
Click to expand...
Click to collapse
Is included on the Unified Layout version of PA. thank to Ayysir.
Related
...that has been haunting me for months now. I've read all the articles I could find out there. Ive tested 402, 403 and now 404 ics and tve bug is still here.. I always end up finding articles saying that I need to torn off my screen then on.. this works for a while then it comes back.. right now im running gummynex 1.0.1 based on 4.0.4 with franco kernel. I'm still getting this unbelievable annoying bug...
Does anybody know about an upcoming fix? If no, is there Any ways to fix this??
-Kim
Sent from my Galaxy Nexus using xda premium
What touchscreen bug?
Theshawty said:
What touchscreen bug?
Click to expand...
Click to collapse
http://www.youtube.com/watch?v=KsYoxZiBTEA
I have it on my Nexus too. Little annoying when you can't properly play games that require touching that portion of the screen. Only seems to affect the phone when it's horizontal.
Me too when playing golden eye with 64 emulator, I can't side step very annoying, if anyone has an answer to this I'd love to know
I tried it and it looks like I don't have this issue at all.
Guys, google galaxy nexus touch screen bug. If you do extensive testing you will notice this. It only happens in landscape mode. Check the youtube clip. I really want this to be fixed so bad!!!!
Sent from my Galaxy Nexus using xda premium
keem85 said:
Guys, google galaxy nexus touch screen bug. If you do extensive testing you will notice this. It only happens in landscape mode. Check the youtube clip. I really want this to be fixed so bad!!!!
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Is this a software or hardware issue?
And no, I cannot seem to replicate this issue no matter what I do.
Theshawty said:
I tried it and it looks like I don't have this issue at all.
Click to expand...
Click to collapse
Same here, I tried getting this to happen for about an hour. Never lost my fingers position.
JaiaV said:
Same here, I tried getting this to happen for about an hour. Never lost my fingers position.
Click to expand...
Click to collapse
The only time it lost my finger's position was when I removed said finger from the screen. ^^
Never had this issue ever since I moved from 4.0.2, and now i'm on 4.0.4. Lastest CM9 nightly build. No multi-touch issue and I do play games that require them.
keem85 said:
Guys, google galaxy nexus touch screen bug. If you do extensive testing you will notice this. It only happens in landscape mode. Check the youtube clip. I really want this to be fixed so bad!!!!
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I've been trying to reproduce that issue since December. Hasn't happened yet.
Dictate said:
http://www.youtube.com/watch?v=KsYoxZiBTEA
Click to expand...
Click to collapse
Lol that's my video
Guys this bug is fixed in 4.0.4, or at least AOKP. I haven't had it since AOKP build 29.
I have been waiting until 4.0.4 became a Verizon OTA update, to update my video that it's fixed.
I have played a bunch of Shadowgun and Pew Pew and never saw this again. I'm confident it's fixed.
Maybe it is indeed fixed in 4.0.4 as I can't remember seeing it in some time.
(AOKP as well).
I had it I think a total of two times...
But for me turning the screen off only provided relief for 10-15 seconds.
I had to reboot.
I had actually forgotten about the bug...
And tried to replicate again with three multi-touch games back-to-back and two multi-touch testing apps back to back...
No problems.
Lucker! Im still having this with gummynex 4.0.4, franco and glados tested... :/
Sent from my Galaxy Nexus using xda premium
Guys -
I installed the Splashtop 2 on my Nexus 7 running AOKP and Trinity Krenel, and it bricked my device twice. Just running the software and suddenly it crashes, then no buttons work. Then the screen starts to flash and it shuts down. I was unable to get into recovery. I need to push a new recovery to get it running back again. This has happen twice today. Anyone else having this issue?
Its bricked?
So you put it in the trash or sent it back to ASUS?
I'm going to go out on a limb here and say this is not related to splashtop.
I had an issue using Splashtop 2 today that freaked me out a little. Going from Sharp to Smooth froze my N7 and when it booted back up, which took longer than usual, the speaker made a faint but distinct "hissing" noise then a louder "tap"
Everything is working again but that's never happened before. Not sure I liked Splashtop 2 enough to bother with it after that.
Hemidroids said:
Its bricked?
So you put it in the trash or sent it back to ASUS?
Click to expand...
Click to collapse
No.. I know how to get out of a jam. The device would not boot afterward the system froze, then rebooting I got stuck at Google screen. Then it wouldn't get into recovery from bootloader I had to flash a new recovery and flash back up. Sounds like it was bricked at the time to me.
Sent from my Nexus 7 using xda premium
tdrussell said:
I'm going to go out on a limb here and say this is not related to splashtop.
Click to expand...
Click to collapse
I would see why you would say this....however this happened twice when using the new splashtop. My set up or system has not changed in days. Only thing that changed was me installing splashtop. Once I stopped using it and went back to the old one. No issues. Someone else n the market review described the same thing to a t.
Sent from my Nexus 7 using xda premium
Installed HD2 this morning and same problem, freeze when changing from sharp to smooth. Hard reset twice, to get it to boot now the speaker sounds like its blown, was streaming some video from the PC. Running EOS + stock kernel.
Something isn't right with it that's for sure, avoid for now is my advice.
Sent from my Nexus S using xda premium
Knether said:
No.. I know how to get out of a jam. The device would not boot afterward the system froze, then rebooting I got stuck at Google screen. Then it wouldn't get into recovery from bootloader I had to flash a new recovery and flash back up. Sounds like it was bricked at the time to me.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Oh......so its not a brick. Might want to change the title.
Splashtop also froze my Nexus 7, fortunately hasn't knackered the speaker or anything. I was going to blame my undervolt though...
sensory said:
I had an issue using Splashtop 2 today that freaked me out a little. Going from Sharp to Smooth froze my N7 and when it booted back up, which took longer than usual, the speaker made a faint but distinct "hissing" noise then a louder "tap"
Everything is working again but that's never happened before. Not sure I liked Splashtop 2 enough to bother with it after that.
Click to expand...
Click to collapse
I had this same thing happen to me. Everything froze up then my Nexus rebooted itself. Other than that the app runs pretty damn good for me. No rooting or roms on mine.
PA 1.97a, Trinity Kernel @ 1640 (ondemand/deadline), Nova Launcher, Dark Jelly Theme.
Daily use out of Splashtop with absolutely no issue. It's one of the things I like best about this tablet.
my only negative view towards the nexus 7 is the influx of noobs that dont know what brick means. i have a g1 with a bad spl flash. that is a brick. you sir just need to flash a factory img. your not bricked.
xxmonsterx said:
my only negative view towards the nexus 7 is the influx of noobs that dont know what brick means. i have a g1 with a bad spl flash. that is a brick. you sir just need to flash a factory img. your not bricked.
Click to expand...
Click to collapse
The only reason he can't access recovery is because of a bug in boot loader 3.34 so its even less of a brick and more of a don't OV and OC
Sent from my Nexus 7 using xda app-developers app
xxmonsterx said:
my only negative view towards the nexus 7 is the influx of noobs that dont know what brick means. i have a g1 with a bad spl flash. that is a brick. you sir just need to flash a factory img. your not bricked.
Click to expand...
Click to collapse
Influx of noobs? I've been around XDA a bit longer than you. I am deeply sorry forum wordsmith for using the word brick not in the fashion you so desired.
Moving on:
I just wanted to get this word out there and just making sure its not my device. I spoke with Splash top and "they're on it." So we'll see :highfive:
Sorry good sir. I do suppose that was a bit rude. I may have taken out my dissapointment with what xda is becoming on you. My bad bud. I'm not here to compare the d!cks bro. I just can't stand seeing all these help I'm bricked threads.
xxmonsterx said:
Sorry good sir. I do suppose that was a bit rude. I may have taken out my dissapointment with what xda is becoming on you. My bad bud. I'm not here to compare the d!cks bro. I just can't stand seeing all these help I'm bricked threads.
Click to expand...
Click to collapse
No harm no foul. I don't hold grudges. Conflict resolution at its best. Thanks for that, means a lot and restores my faith in people. :laugh:
Harry GT-S5830 said:
The only reason he can't access recovery is because of a bug in boot loader 3.34 so its even less of a brick and more of a don't OV and OC
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
What is this bug you speak of?
Also, OC and OV is causing issues? Sorry If i dont know about this just yet, is there a thread that speaks about this?
Knether said:
What is this bug you speak of?
Also, OC and OV is causing issues? Sorry If i dont know about this just yet, is there a thread that speaks about this?
Click to expand...
Click to collapse
Try acessing recovery through boot loader on a healthy N7 and not plugged in, you will find that you can't access recovery. There's quite a few "Q" threads saying that I OC to 1600 and overvolted by 50MHz across the board, and my nexus fried? Why is this??
Sent from a Nexus 7 using my fingers
I've got the same problem with Splashtop and Nexus 7. Original ROM, no root. After switching smooth<>shart Nexus just reboots. Also there seems to be nothing interesting in logcat.
qrees said:
I've got the same problem with Splashtop and Nexus 7. Original ROM, no root. After switching smooth<>shart Nexus just reboots. Also there seems to be nothing interesting in logcat.
Click to expand...
Click to collapse
I seems to be fixed after todays update, but it's still strage that single app could crash the whole device.
Hey. After I flash a new rom, the phone is super quick and respones very well. Buy after a few days, it starts to get laggy. When I am presaing the soft keys it takes a couple of seconds to respond, apps loading times can reach about 20 seconds, contacts loading too. I am using the GSM Gnex with CNA 3.8 rom and franco kernel r298. The lags occurred with XenonHD too. Dont get me wrong, I am not complaining about the developers, I am just trying to figure out if I am doing something wrong.
Sent from my Galaxy Nexus using Tapatalk 2
bar_rodoy said:
Hey. After I flash a new rom, the phone is super quick and respones very well. Buy after a few days, it starts to get laggy. When I am presaing the soft keys it takes a couple of seconds to respond, apps loading times can reach about 20 seconds, contacts loading too. I am using the GSM Gnex with CNA 3.8 rom and franco kernel r298. The lags occurred with XenonHD too. Dont get me wrong, I am not complaining about the developers, I am just trying to figure out if I am doing something wrong.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Are you rebooting your phone or just leaving it on for weeks at a time?
I remember someone saying it has to do with the zram optimizations in roms and kernels. at first it makes things faster and the the idea implemented is good in theory but over time it makes things unbearably slow. i dont know the technical reasons for this, someone with more knowledge than me may be able to explain it.
Sent from my Nexus Prime using xda premium
I forgot to mention, its getting worse when I download or update app from the Play Store. During the download process the phone realy lagg.
063_xbox, the phone restarts itself sometimes when I use it...
Sent from my Galaxy Nexus using Tapatalk 2
bar_rodoy said:
I forgot to mention, its getting worse when I download or update app from the Play Store. During the download process the phone realy lagg.
063_xbox, the phone restarts itself sometimes when I use it...
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Obviously downloading from the Play Store is using system resources (RAM, a % of the processor etc.) so a slow down is to be expected.
The phone restarting itself =/= to rebooting it regularly. Just like your computer you shouldn't leave it running 24/7. Sometimes you just need to give your phone a restart.
I think the lags are related to the heatcof the Gnex. Maybe the my cheap case makes it worse. I will check without case so it have more contact with the air. I will report the results.
Sent from my Galaxy Nexus using Tapatalk 2
I've noticed the same lag after few days. It's really frustrating to see your phone very fast and then kind of choppy....
Sent from my Galaxy Nexus using xda app-developers app
It looks almost like a memory leak. (That was a big problem on exynos devices runing cm10). It happened to me today (latest nightly cm10), Once my free ram was less than 100 mb the phone became noticeably less responsive.
Sane here!!! Thought it was just me... lol. I was running black bean baked! I love it but became super laggy! Almost threw it across my room lol. But just clashed slim bean and hope its bad ROM coding :-/.
Sent from my Galaxy Nexus using xda premium
I understand that custom roms do have great features but let me tell you something, after I switched from the S3 I decided not to flash any rom, I just used the nexus toolkit to root it and of course install franco kernel, since then the experience has been amazing, I'm just very careful with the apps I install, cheers!
Sent from my Nexus Prime JB 4.1.2
I've experienced the same on about every JB setup I've tried. A reboot tends to purge assets and get me truckin' again for several days though.
I recommend keeping it stock you people, stock almost never lags unless u use the google+ app
Sent from my Galaxy Nexus using Tapatalk 2
Let me just chime in with the same advice as the previous poster: Try the stock rom. 99% of your problems will magically disappear.
lsv-1 said:
I understand that custom roms do have great features but let me tell you something, after I switched from the S3 I decided not to flash any rom, I just used the nexus toolkit to root it and of course install franco kernel, since then the experience has been amazing, I'm just very careful with the apps I install, cheers!
Sent from my Nexus Prime JB 4.1.2
Click to expand...
Click to collapse
Wow! If you only knew that no matter which ROM you're running, the majority of bugs are caused by the kernel. You did not make a smart choice on kernel my friend.
Sent from my Galaxy Nexus using xda premium
Soldier-2Point0 said:
Wow! If you only knew that no matter which ROM you're running, the majority of bugs are caused by the kernel. You did not make a smart choice on kernel my friend.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Ok, so, what kernel you think is a smart choice my friend?
Sent from my Nexus Prime JB 4.1.2
lsv-1 said:
Ok, so, what kernel you think is a smart choice my friend?
Sent from my Nexus Prime JB 4.1.2
Click to expand...
Click to collapse
Stock, of course! :wink: :wink:
063_XOBX said:
Are you rebooting your phone or just leaving it on for weeks at a time?
Click to expand...
Click to collapse
this..
Soldier-2Point0 said:
Stock, of course! :wink: :wink:
Click to expand...
Click to collapse
Yup u are right. Many people used to tell that Franco kernel is the best and stuff but even that after using for a few days gets slow whereas in stock all that crap doesn't happen. I still use Franco because games work smoother on it compared to stock. Even the battery life is inconsistent. Just try stock after weeks and Franco right after a reboot still stock will be overall faster and smoother.
Sent from my Galaxy Nexus using Tapatalk 2
Soldier-2Point0 said:
Stock, of course! :wink: :wink:
Click to expand...
Click to collapse
LOL, unfortunately I need franco's kernel (or any other custom kernel) to do things that the stock doesn't allow, i. e modify the colors of the screen (I hate yellowish whites) use pgm2 aka slide to wake, use louder patch and modify specific cpu parameters.
Sent from my Nexus Prime JB 4.1.2
lsv-1 said:
LOL, unfortunately I need franco's kernel (or any other custom kernel) to do things that the stock doesn't allow, i. e modify the colors of the screen (I hate yellowish whites) use pgm2 aka slide to wake, use louder patch and modify specific cpu parameters.
Sent from my Nexus Prime JB 4.1.2
Click to expand...
Click to collapse
Yeah, that the point. I want to change the screen color settings... Franco's kernel allows you to do that.
I am going to change to team EOS rom and check it for a few days. If I have problems with that one I am going back to stock rom.
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