So, yesterday I got my nexus, and since then i'm experiencing random reboots: i've got 2 of them in the first day and 3 today (so far).
Generally it happens when the nexus is from 75% to 90% charged and I'm using it. It seems it doesn't matter which app I'm using, and the system is stock, no root/mods/whatever.
I've already cleared cache partition and even tried to re-insert the micro sim (I've read somewhere that a faulty installation of the sim may cause reboot troubles) but nothing changed.
Said so, I think it's an hw problem; top suspects: battery and memory.
Here's my last_kmsg View attachment last_kmsg.rar It seems to me that there are memory issues, but I'm pretty noob so can someone look at it and let my know if there is something useful to find the cause of the problem? Thanks :fingers-crossed:
Bump
so prior to being on venom 4.2, i was on venom 3.xx. i had no problems prior.
i flash 4.2, and had no problems related to the camera not working. i had other problems though, after reflashing 4.2 those problems went away, but now a new problem came up.
after a restart, i can use the camera maybe once, or take one photo. after that, the screen through the camera will be frozen on screen. i can still take pictures, but it will only be off what is on the screen. after closing the camera, or force closing it,upon trying to open the camera app again, it barely loads, then force closes automatically and i get an "unable to start camera" bubble on screen. i can see only the grid outline of the camera, off center and such very briefly ontop of my wallpaper.
i can do a reset on my phone, and resume taking pictures, sometimes i am fine to continue, other times its the same problem. this is a very common recurring problem for me.
looking at my apps, i see 2 cameras installed, one is the new 5.0, and the other is the old 4.xx camera. i have frozen the 4.xx camera before through titanium, and it doesnt fix it. should i uninstall the 4.xx camera altogether?
subsequent reflashing of this rom doesnt fix this issue. and i dont know what else to do rather than reflashing the rom from a blank slate. previous reflashings have been on top of the current rom.
i would rather not have to start new as this phone has crappy amoint of space, and i cannot back up all my apps and settings.
i dont know if it is kernel related. prior to 4.2 i was using elemental x, after 4.2 i switched to beastmode since i wasnt soff.
is there perhaps a way i can manually start the camera through root browser?
If you've got both versions of camera in your app drawer I'm guessing you dirty flashed the ROM, which has most likely caused your problems. Clean flash the ROM and see if it fixes your issue. This is why I'm totally against dirty flashing anything.
I don't understand how you don't have space to back up your apps, I have a backup of every app I've ever used and still have tons of space left over. The fact that you mention backing up settings troubles me, restoring system settings after flashing a new ROM will more than likely cause problems for you.
When you're flashing a ROM don't do it the lazy way, do it the right way, perform a full wipe (cache/dalvik cache/factory reset/system) and start clean. It only takes a few minutes to setup your ROM from scratch. Restore your apps but don't restore any system data.
Sent from my Evita
thanks for the reply.
as suggested, I did a complete reset. wiped the caches, factory reset, and system reset.
installed from scratch. But i am still having the camera issue?
now its just not loading at all. black screen, then close. no error message. and no unable to start message.
could it perhaps be a hardware issue at this point?
without restoring anything, under apps, I still see two instances of the camera app. one at 5.1, and one at 4.2.2. can anyone confirm this is normal?
the only thing out of the ordinary, within the past few months, my phone has been getting crazy hot at times. specifically right below the lens of the rear camera. I was getting this heat from charging, or even certain apps. Definitely attribute that to the age of the phone. as apps that ran smooth when the phone was new, no longer are so.
I dont know if the heat can cause hardware damage?
also, not sure how relevant this is in the context of my situation. but apps that use the camera do not work either when the camera is needed, such as snapchat and instagram.
Since the clean flash did you at least end up with only the more recent version of the camera in your app drawer? You could be looking at some kind of hardware malfunction, or even a problem with the ImageSense proprietary chip that is utilised to operate the camera. The fact that the camera works sometimes would suggest that all is not lost. Have you tried flashing an aosp ROM to see if anything changes? I'd suggest trying that, and if that doesn't work you should try running an RUU to see if a completely stock setup will help.
The phone heating up near the camera lens isn't abnormal for this device. The amount that it heats up can change significantly depending on the ROM/kernel that you're running. You should definitely try not to use CPU intensive apps while the device is charging.
Sent from my Evita
timmaaa said:
Since the clean flash did you at least end up with only the more recent version of the camera in your app drawer? You could be looking at some kind of hardware malfunction, or even a problem with the ImageSense proprietary chip that is utilised to operate the camera. The fact that the camera works sometimes would suggest that all is not lost. Have you tried flashing an aosp ROM to see if anything changes? I'd suggest trying that, and if that doesn't work you should try running an RUU to see if a completely stock setup will help.
The phone heating up near the camera lens isn't abnormal for this device. The amount that it heats up can change significantly depending on the ROM/kernel that you're running. You should definitely try not to use CPU intensive apps while the device is charging.
Sent from my Evita
Click to expand...
Click to collapse
no, the clean flash still left both cameras in my "manage apps", i have never seen two camera icons in my app drawer.
as of right now, i cannot get the camera to run in any way. even with a reboot. The only reason I really did the clean reflash, was because the camera wasnt working at all today. I did a bit more digging around, and it seems like this is a fairly common problem for the one x. there seems to be quite a few people, even on stock roms, that cannot seem to remedy this. and a few have chalked it up to a hardware problem, some have been confirmed, and others not so much.
I really dislike flashing this phone. ive encountered so many hiccups and scares(mainly a few soft bricks here and there). I really prefer the "if its not broken, it doesnt need fixing approach" here, granted my camera is shot.
one of the reflashes today was giving me wifi errors with wifi not even turning on. I really want to avoid potentially more problems, unless a fix is deemed more definite. Thank you for all your help timmaaa!
im just in need of a new phone now. so many problems, and so many things the phone can no longer do effectively. random reboots, overheating, battery life, even the charging rate. this phone has become crap. Ive always hated the lack of expandable memory. I really dont know why I didnt choose a different phone over this at the time.
i really like the htc one, but i feel like many of the nuisances in the one X will follow over.
chinaman_chong said:
no, the clean flash still left both cameras in my "manage apps", i have never seen two camera icons in my app drawer.
as of right now, i cannot get the camera to run in any way. even with a reboot. The only reason I really did the clean reflash, was because the camera wasnt working at all today. I did a bit more digging around, and it seems like this is a fairly common problem for the one x. there seems to be quite a few people, even on stock roms, that cannot seem to remedy this. and a few have chalked it up to a hardware problem, some have been confirmed, and others not so much.
I really dislike flashing this phone. ive encountered so many hiccups and scares(mainly a few soft bricks here and there). I really prefer the "if its not broken, it doesnt need fixing approach" here, granted my camera is shot.
one of the reflashes today was giving me wifi errors with wifi not even turning on. I really want to avoid potentially more problems, unless a fix is deemed more definite. Thank you for all your help timmaaa!
im just in need of a new phone now. so many problems, and so many things the phone can no longer do effectively. random reboots, overheating, battery life, even the charging rate. this phone has become crap. Ive always hated the lack of expandable memory. I really dont know why I didnt choose a different phone over this at the time.
i really like the htc one, but i feel like many of the nuisances in the one X will follow over.
Click to expand...
Click to collapse
There's nothing wrong with this phone. Given the right amount of knowledge and care the thing doesn't skip a beat. Even though there is no such thing as a soft brick (a phone is either bricked or it isn't), whatever it is that people experience in those so called "soft brick" instances is caused by user error 99% of the time. I've seen it time and time again.
Any phone available on the market can experience any amount of issues if it isn't handled correctly. You got unlucky and your camera is most likely shot, but any other problem you've encountered comes with the territory of flashing unofficial firmware and software, it isn't anything wrong with the device itself. These are possibilities you need to be comfortable with if you're going to modify your device.
Yea, I assumed there were gonna be risks when I rooted my phone. Dont know if any of the issues I had were related to rooting or not.
The soft brick scare I had was due to a flash that went wrong for no apparent reason.
another update on my phone. I noticed my front facing camera has no issues whatsoever. unluckily for me, I cannot even access my camera, to toggle to the front facing camera to even attempt to check it out. Instagram also does not allow me to switch either, it just gives me an error saying it cannot connect to a camera, then closes. snapchat's rear facing camera is just a black screen for me, but it doesnt force close, so I am able to toggle to the front camera, and it works just fine.
is there a setting or something I can modify, for now, so the front facing camera is the default?
my brother's one x recently went out this year too. I am gonna try to salvage his camera, and see if it will fix my problem.
I have not taken apart this phone yet, is the camera soldered or held in with connectors?
Have you tried an RUU yet like I previously suggested?
Sent from my Evita
chinaman_chong said:
I really dislike flashing this phone. ive encountered so many hiccups and scares(mainly a few soft bricks here and there). I really prefer the "if its not broken, it doesnt need fixing approach" here, granted my camera is shot.
one of the reflashes today was giving me wifi errors with wifi not even turning on. I really want to avoid potentially more problems, unless a fix is deemed more definite.
Click to expand...
Click to collapse
If a couple hiccups and scares are too much for your, then it might be that modding phones is not for you. These types of things happen time to time to even those experienced with flashing ROMs. Occasional setbacks and troubleshooting is just part of the game. If that is too much for you, than don't play.
As timmaaa already mentioned, failure to boot is not the phone's fault; and its almost always a matter of user error and not following the procedures properly.
chinaman_chong said:
im just in need of a new phone now. so many problems, and so many things the phone can no longer do effectively. random reboots, overheating, battery life, even the charging rate. this phone has become crap. Ive always hated the lack of expandable memory. I really dont know why I didnt choose a different phone over this at the time.
i really like the htc one, but i feel like many of the nuisances in the one X will follow over.
Click to expand...
Click to collapse
Random software errors like random rebooting, overheating, etc. are often easily remedied with the proper steps. They are likely not issue with the phone itself, but rather a result of improper steps while flashing the ROMs. I've flashed many ROMs on this device, and have never suffered any such issues that I couldn't solve easily.
As for your other complaints about the phone (lack of expandable memory, why you didn't choose another phone), I don't know why you even posted them, as they are not constructive. Those still on this forum are mostly here because we love the phone and remain loyal to it. Your comments aren't going to help your issue, and will only annoy fans of the device. Better to keep such comments to yourself.
If you hate the phone so much, go buy another one and be done with it. But crying about it isn't going to solve anything.
I would suggest you follow timmaaa's advice, and flash the appropriate RUU to "start over". S-off is highly recommended before RUU, as running certain RUUs with S-on and SuperCID will brick the phone.
I have the same device and the same problem.
It doesn't depends of firmware or kernel or camera app..
I thought it's hardware problem but it is not. Because i was changing the camera module and it doesn't helps((
Don't know what to do with this issue(
The Moto G is prone to all sorts of little problems, most of which gradually grow into system instability and performance issues. Generally these are fixed with a simple factory reset, but for some reason that sometimes fails to help. I was having a lot of trouble with my phone, overheating, aforementioned performance and stability, etc... and a factory reset seemed to help, but as time went on and I used my phone, they would return.
My last problem, about 4 or 5 days ago was that my phone just constantly kept resetting itself, in addition to the UI crashes I was having before that. After desperately trying to factory reset and clear the cache and all sorts of stuff, I got nowhere. It would hang up at the factory reset process and just keep going forever. I eventually decided to use the reformat option in TWRP and now everything is great. Time will tell if it holds, but it seems solid.
The major concern I have right now is the root cause. I think that many Moto Gs were shipped with bad memory, which I will test when I look for/find an app for it, which as anyone experienced with computer repair would know can lead to all of these issues and even data corruption, which I think is what might be causing these weird issues. So if anyone has anything to add or correct me on, please be my guest. But for all of you out there struggling with these bugs, give it a try and see if it helps.
Hi,
Sorry if this has been posted before, I didn't find anything related on here though.
Since updating my Nexus 5 to Lollipop when it was released, it has been a huge annoyance most of the time. Fresh after a reboot it's fine but the longer I use it (it usually starts after about a day), the worse it gets. It lags badly, sometimes freezes and apps get killed constantly (even if I only go back to the homescreen for a second, apps are being closed immediately). I did a factory reset which didn't help for very long, tried a different ROM (Paranoid) and regularly clear the cache (which also helps a bit but not for very long either). The RAM is never fully used and I have several GB of disk space left, so I can't explain why it's behaving like this.
I don't know what else to do or to try and while I found a couple of articles via Google, I didn't come across any solutions that helped. I hope you can help me, I don't want to go back to Kitkat...
Thanks,
Manu
Pretty sure you're talking about the memory leak issues that MANY people have experienced. 5.1 will hopefully resolve a lot of them.
This was my first guess, too. But wouldn't a memory leak use up all the RAM? I usually have a fair chunk free even though my phone is barely usable anymore. Nevertheless, I will flash the factory image this weekend and hope for the best!
I am on the latest stock 8.1. I've noticed recently that when I download "large" files (let's say over 200mb), the phone will often become slow and unresponsive - and I've even had it force reboot. This can happen when downloading movies on Netflix to view offline, or when downloading files through Chrome for example.
The larger the files, the worse it becomes... The time the phone kept rebooting, the file was over 1GB. I don't know exactly when this started, but I'm sure I used to be able to download movies on Netflix without any problems.
Has anyone else noticed this?
surrealjam said:
I am on the latest stock 8.1. I've noticed recently that when I download "large" files (let's say over 200mb), the phone will often become slow and unresponsive - and I've even had it force reboot. This can happen when downloading movies on Netflix to view offline, or when downloading files through Chrome for example.
The larger the files, the worse it becomes... The time the phone kept rebooting, the file was over 1GB. I don't know exactly when this started, but I'm sure I used to be able to download movies on Netflix without any problems.
Has anyone else noticed this?
Click to expand...
Click to collapse
Not had this problem. I'd say try reflashing stock tbh.
I am having this same issue. I'll be downloading a large file and the phone will lag and then finally freeze up and then it'll reboot. Have you still been having the issue?
sapplegater said:
I am having this same issue. I'll be downloading a large file and the phone will lag and then finally freeze up and then it'll reboot. Have you still been having the issue?
Click to expand...
Click to collapse
Yeah, still have it. I don't do many downloads so I haven't got around to a factory reset yet. Maybe that'll fix it.
It's almost like the phone completely runs out of resources... I've monitored RAM usage during the download though and it seems OK. Really odd one... maybe a future update might sort it.
Sorry to bring an old thread back from the dead, but I have this issue too, and I can confirm that a factory reset does not fix it.
Mocha_Bean said:
Sorry to bring an old thread back from the dead, but I have this issue too, and I can confirm that a factory reset does not fix it.
Click to expand...
Click to collapse
I'd only just noticed there was another reply to this. Indeed, a factory reset doesn't solve it - I think there's something fundamentally wrong with the OS trying to write large files to storage. For most people this won't be an issue as the average phone user is unlikely to download 1 or 2GB at a time. There are other posts related to trying to copy large files (such as movies) to their phone over a USB cable so I suspect it's not just related to downloading over a network. It's more of a general I/O issue - and it's really annoying when you need to genuinely download such large files.
surrealjam said:
There are other posts related to trying to copy large files (such as movies) to their phone over a USB cable so I suspect it's not just related to downloading over a network.
Click to expand...
Click to collapse
Yeah, I've had the issue with USB file transfer too.
Any solutions to the problem? My S8 has now been doing this for the past 2 months
MikeG-104 said:
Any solutions to the problem? My S8 has now been doing this for the past 2 months
Click to expand...
Click to collapse
Not that I'm aware of, sorry. I'm on the latest 9.0 release (November update for OG Pixel) and it's exactly the same. I noticed a slight improvement after a factory reset but it wasn't a permanent fix. I'm not sure if the issue gets worse the less free space is on the phone... I'm currently running at about 85% used storage as I'm on the 32gb model.
I'm having the same problem. Is there any way to solve it or work around it?
Still have this problem, I wonder if Lineage OS would fix the issue? If anyone could test this, that would be amazing. I'm on stock 8.1 now (don't want to upgrade) and I'm glad to know it's not my version of Android. The issue happens when the phone tries to write large files to the storage ie. downloading very large apps (guesing about >500mb?) or recording high resolution video on the camera. Recording 4K video softbricks the phone into a bootloop, I switched it to 1080p but I don't want to test if it still bricks the phone, but I did notice that at 1080p60 I could record <30 sec and be okay. My phone storage is always around or above 70% full.
Hey guys who are experiencing this issue - this is NOT due to the device not accepting large files. It's a sign of emmc going out. The way I proved this on one of my bootlooping pixels is unlocking the bootloader and flashing for example any kind of rom. If it crashes right away while flashing, this is proving that there is a defect in the emmc. This issue is very lightly documented but it was very tragic to the 6P and it feels very weird that this issue has been ported over to the Pixel because at the same time, it looks pretty rare and pretty common. I'd say back up all your stuff immediately and if you are on warranty get a RMA because this is completely ridiculous. This seems to be more apparent in devices that were exposed to moisture, even though it would be a extreme death if it was dropped in water, it looks like the device can die very easily from simply moisture. Hardware fails over time, my bro in law said that best.
Is there truly no solution to this issue?
I'm using an UMIDIGI A7 Pro and I have this problem
Note 3 32gb here this sounds like what I am having issue with my phone when I write to micro SD anything over 10 mb it reboots. Saving to emmc does not only when writing to micro SD. Moving it from onboard to SD triggers it too. After reboot it transfers and downloads fine.
Got a 512gb card today formatted in phone storage and my crashes are gone.