After completing the update and successful rooting I am experiencing many issues throughout my devices that I have not ran into on previous updates.
The main problem is that every 5 - 10 minutes my device freezes for a few seconds then reboots itself.
I have tried many things t fix this. Flashing back to NCE then updating again to OA1 and Factory Reset after rootation still did not seem to fix. I've tried Unformat my external SD card and turning off auto sync. Still no fix.
Other problems I am having are thing such as applications beginning to force close. Even the google keyboard gets this problem every now and then.
After my device was updated and rooted I did the usual and clean it up as I did on previous versions and never had this problem until now.
Related
When I try to enable WIFI on my G1, for a couple of seconds it says: enabling WIFI, but then the phone becomes unresponsive (for about 1 second) and it reboots.
IIRC the problem started when I upgraded to the new CynogenMod ROM (4.1.99, but not sure), but it doesn't seem to be linked to the ROM.
I have always used CyanogenMod and update with every new version.
I tried to go back to the default HTC rom, but this doesn't solve the issue.
Does anyone know what may cause this or give me some tips on how to debug this?
I tried to run 'adb logcat' but it shows no info.
The exception browser in the CyanogenMod is also empty.
I don't know what else I could try.
Some extra info:
HSPL 10.95.3000
Radio 2.22.19.26I
CynogenMod ROM 4.1.99 is not the newest. Wipe, flash the htc image, flash cyan's newest and try wifi again.
No, I know, but I think that's when the problems started.
Latest version I installed was 4.2.13
I have installed the RC7 dreaimg.nbh now (used to root the G1), and when I try to enable WIFI on this rom, the phone doesn't reboot, it keeps working, but I get an error saying that WIFI could not be started.
I'm also having problems with wifi causing random reboots. For me it usually happens once a day if wifi is enabled and not at all if its disabled. Once the phone reboots, it hangs at the android screen and I have to do a battery pull to reset it. The problem also appears to be rom independent. Very weird, it has started happening in the last few weeks and I can't think of anything that has changed.
mattb3 said:
I'm also having problems with wifi causing random reboots. For me it usually happens once a day if wifi is enabled and not at all if its disabled. Once the phone reboots, it hangs at the android screen and I have to do a battery pull to reset it. The problem also appears to be rom independent. Very weird, it has started happening in the last few weeks and I can't think of anything that has changed.
Click to expand...
Click to collapse
This is consistent with my experience as well. By far, the VAST majority of spontaneous reboots that have occurred on my phone have been when using wifi. Some of the older Cyan ROMs were really bad about this, but this continues to occur (although much less frequently) regardless of the ROM. I am presently using SuperD and have had one reboot in the past week.
This seems to happen most often when using the wifi heavily; for instance, I get a reboot probably every 3rd or 4th time when I'm doing my weekly podcast downloads. I don't remember any reboots when just surfing the web or downloading apps, though.
I have never had this happen when I was running cyan.
Are you wiping everything? Even EXT and dalvick?
Are you using any other apps when this is running and rebooting? Perhaps an offending app?
You should also open ADB and run ADB Logcat and try to replicate the issue and try to get a log submitted so the dev can help determine what is causing this issue.
I wiped everything and even without any apps installed, it just reboots.
adb logcat doesn't show a thing when the phone reboots, it just exits.
touch screen on milestone stopped working right after downgrade from CM7 to 2.1 or even 2.2 and now when i try to go back to cm7 i get this weird bootloop
I've got a similar issue, but not permanently. I'm using stock froyo and for some reason touchscreen is not working or working improperly after turning on screen from lock. I need to wait a couple of seconds, turn on the screen once more and most of the time it's fine. Any advice?
both of you,
format your SD CARD/PARTIONS when you are downgrading.
some files from previous ROMS can be affecting the STOCK ROM functionality when it starts fresh after fresh install.
happened to me a couple a times,
just reinstalling (properly) solves this issue.
Right... so my phone, for some reason most of the apps on my phone decided to start crashing. Usually on startup I have to hit force close on about 15 apps. I had never until this point flashed my ROM, rooted my phone or anything.
I started of by trying factory reset but it didnt reset anything. I had to run the setup wizard (all the time the apps were all crashing) but when it finished I was still seeing all my apps. So i thought it might be a good idea to uninstall all the downloaded apps but when I do so they just come back when I reboot.
I have since tried flashing the firmware and rooting the device as per the instructions on android soul to flash to 2.3.5
However I am still facing the same problem. Right now I can't get past the setup wizard crashing in a loop.
Any idea's or advice?
I dabbled in a few custom roms when I first bought my note mainly note 7 ports. After they started having problems with each battery dying at 50%,random reboots etc.. I tried to go back to stock but when I tried to odin to QC1 it kept failing and failing so I odined to the newest update QC2 and it finally passed.I did like three factory resets and I was back on stock and happy until i started having random issues. Every time I'm in a phone call after like a few minutes go by the phone would randomly reboot itself then I would have problems where on facebook or snapchat it would freeze up and I would have to pull the battery.Then I would have issues with the phone battery not getting down to 0% and dying but dying at 50 or 25%.Also, I keep having to do the freezer trick to get my phone turned back on again. Ive tried every kernel to fix these issues QC1,QC2.PE3.PJ2,BEASTMODE ETC.. and nothing works,also im stock rooted qc2 if that helps running pj2 kernel if that helps..
Hey guys, I've encountered a thorny problem on my wife's N910T3, and am running out of ideas about what this could be... so, could really use some help.
Some background: The phone's been working fine for over a year of ownership, mostly on the stock ROM, which gets pretty laggy at times. A few weeks ago I installed a custom ROM (the Acapolypse-X N7 port) to improve performance, and for the past few weeks it's been working perfectly fine on the custom ROM no problem.
Today, when my wife went to check Twitter, the phone crashed and started bootlooping. I had seen a similar issue on my Note 3 before (which turned out to be a specific issue with the kernel I was using), so I figured I would just go into recovery, flash a different kernel or at worst, do a clean install of the ROM.
That's when things started getting weird: The phone would crash while INSIDE recovery during ROM installation (I've never seen a phone crash inside recovery before...) After failing to successfully flash a ROM or, even in cases when it succeeds, fails to boot, I decided to do a full flash back to the latest unmodified stock ROM (since I couldn't find an ODIN-flashable image to download, I used Samsung Kies for this - typically this resolves any kind of left over from previous installations).
On the first attempt, it succeeded - the phone booted into the stock ROM and I was able to start customizing settings. Figuring the issue has been resolved, I went ahead and attempted to root by flashing TWRP through ODIN, and that's when the phone went back to rapidly bootlooping again (it reboots every 2 seconds, I can't even get into recovery when this is occuring). The only way I can return to Recovery is by flashing it again in ODIN (typically this trick will only work once; upon rebooting the phone after that it is prone to start bootlooping again).
Based on the symptoms I suspected the NAND going bad. However, I receive no emmc read/write errors during flashing - all write operations in ODIN results in success and my friend even ran a full storage check via ADB and this phone just doesn't seem to have any bad sectors (I almost wish it were since that would resolve the mystery).
Anyone have any ideas what may be the problem? I have a decent amount of experience installing custom roms on my phones and troubleshooting installation issues, but I've never seen anything like this (crashing/bootlooping directly inside recovery).
I'm sure there are several possibilities that could be software related. However, I've had this issue on a couple of my older phones and it just turned out that the power button was sticking. Just had to pull the phone apart and clean it.
If nothing else seems to work for you, it wouldn't hurt to check this.
PS: I have 4 boys who like to play on the devices with sticky fingers.