ok so i have moved up to gingerbread, but i seem to be having a problem. for whatever reason after about 2 weeks of running gingerbread roms they reboot themselves then as they are booting back up the boot animation will freeze on me. no one has been able to figure this out yet but i have at least been getting logs of it.
both loop issues are caused with roms UD 3.0 beta/rc1/rc2 and liquid slayher gingerbread.
clearing cache - doesnt work
clearing system- doesnt work
clearing boot - doesnt work
reflashing rom after doing all of this - doesnt work
clearing my data - works. but this is getting annoying having to set the phone back up every two weeks. Froyo roms works perfect with some FC's here and there. but i uploaded all 5 logs i have.
mediafire.com/?ihdseljud1ctgs1
logs logcat1-4.txt are UD 3.0 and logcat5.txt i just did with liquid slahyer.
please someone shed some light on the source of my problem because i have a feeling its either dalvik issue or a app issue.
Related
Looked at the sticky, but did not see this issue. It was happening on my cyan builds once I went to donut. I swapped, updated all, wipe, install per instructions, but the prob found me again. This time I am not the official 1.6(DRC83, 2.22.19.26I) Anyone else have this happen to them?
Fixes?
Okay, so the time ranges between 30 seconds and a minute.
From what I am seeing, I may have to revert back to stock settings and give it a go. If that works, then I will attempt to ROOT again.
I only began having this issue after I upgraded to 1.6 via cyanogen.
I swapped ROMs hoping to solve the issue ( thought it may have been b/c of the experimental/beta version)
But after being on this build for one day, I am already experiencing the issue again. I even went as far as repartitioning and wiping before I started so it would be a clean slate.
ljnick19, this is an interesting problem. What call settings are enabled for you when this happens?
derfolo said:
ljnick19, this is an interesting problem. What call settings are enabled for you when this happens?
Click to expand...
Click to collapse
I have made zero changes to the standard setup there. All is normal. I have not fully customized since I applied the ROM b/c of time constraints. Just getting basic apps back on from the market.
ljnick19 said:
I have made zero changes to the standard setup there. All is normal. I have not fully customized since I applied the ROM b/c of time constraints. Just getting basic apps back on from the market.
Click to expand...
Click to collapse
The HTC recovery may have messed your radio up. Try reflashing the radio.
Thanks for the input! I was worried no would have any ideas. I'll give that a shot. Now when reflashing the radio, do I need to do the whole-radio, spl, rom, wipe thing? Or just radio?
I am also using Ra v1.2.2 recovery, could that be causing issues w/ 1.6, Donut ROMs?
One more issue to add: AdvancedLauncher (processandroid.process.acore) has stopped unexpectedly. FC almost every time i press the home button. Made the mistake of making advanced launcher my default home button action...
For the launcher make sure you have the latest version. Then reinstall or run fix permissions. U only have to flash the radio, and the recovery should only affect flashing the roms
Thanks a mill for the help, I really thought this was going to fall flat. I'll attempt later this afternoon and post results.
For those of you that took a moment to not only read, but to assist, THANK YOU!
Results are:
I went from OTA 1.6 to Cyan 4.1.999
I wiped and repartitioned the sd as well as redoing the radio
So far, I have not experienced any FC's. Unfortunately, I have not made a lot of calls either. Crazy thing was that on the OTA build today, calls seemed to be functioning, but the FC's were excessive.
I also ran fix permissions as well as cleared the dalvik cache.
Again, thanks for the support. I hope to pass it on if I am ever able to help, it is appreciated!
LJ
i have had my ATT N1 for a few months now and all has been great. I rooted awhile back and have been using Cyanogen 5.0.7 to great success. I have the pershoot kernal and never really had any issues.
Well, that has all changed. Recently I have been rebooting any many different occasions. It almost always does it when I am in Maps and navigation, which is not good because I need it in my life having relocated.
I have decided that maybe I will look to update my Cyanogen or maybe go over to 2.2. I did this today and still having these issues. I tried Kang and it still rebooted randomly and when I tried Modacos r17 it just would keep rebooting at the setup screen. I think that has to do with not having the stock kernal.
Any clues as to what is happening? I really need help and do not want to stop using Android, but I need my phone to be reliable.
If it happens on any ROM and with no correlation to anything - sounds like HW problem.
Did you use overclocked kernel?
I do have a overclocked under volted kernal
sounds like bad sw. get back to stock 2.1 update 1 (if you can) and see if your phone is stable...
WIPE all ( everything ) , and flash 2.2
http://forum.xda-developers.com/showthread.php?t=692609
Follow those 3 easy steps there !
Does your phone lock up (unresponsive) before rebooting?
Phone doesnt lock up. I tried wiping evertyhing but could not wipe the sd partition. Is that necessary? I have done full wipe's (data, dalvik, & cache) and still had similar results. I have updated my kernal to the newest pershoot and I installed Kang .9b1 and so far have only had 1 rebbot. It happened when I was in the browser and went to a flash heavy site to see how it worked. Is there any 2.2 roms that keep it close to stock? I am not a total fan of adw launcher.
Have a look in this thread,
http://forum.xda-developers.com/showthread.php?t=703687
I'm really determined to figure out what is causing this issue for so many people! I've managed to cure my reboots for the time being, and it seems it is kernel related. That said, we need as many people as possible to give feedback as experiences seem to differ in regards to the ROMs and Kernels people are using.
Regards.
I looked over that thread and see some similarities but it is still not totally consistent with my issues. I am running Kang now fine but still have reboots that I won't call so random anymore. It happens when I use Maps for the first time, and definitely when I go to a flash site on the browser.
I cannot successfully use any other ROM since once I install it it goes into boot loop. This is driving me crazy and do not like the thought of being stuck to one ROM since it is the complete reason I bought this phone.
I'm posting here because I don't know what else to do, my phone freezes using any froyo rom. It happens randomly and sometimes will not happen until I reboot the phone, but it makes my phone pretty much unusable. I've tried the leaked froyo rom, BB, CM 6 1&2 and countless others. I've tried wiping data / cache and formating the SD card (worked until i put my music back on), and I'm about to just try stock 2.2 and exchange it for a new one if it wont work.
Anyone else have this problem that could help me?
One thing I didn't see you do...
Have you at all root your phone to install the desired froyo rom for your phone?
Yes I am rooted, I'm currently on CM 5.0.8 and very happy but I would really like to get froyo working.
Alright. This is what I've done to get Froyo working on my Droid: I rooted my phone, downloaded BB v4 and changed the name of the file to update, installed Rom Manager on my phone(then found out I can download the roms from here as well), reboot into recovery through rom manager, wiped data & cache, selected install zip, then selected reboot phone. It took a bit to register but it converted over with BB v4.
I think I've found my problem
droidforums.net/forum/tech-issues-bug-reports-suggestions/67526-music-sd-card-causes-bb-4-freeze.html
this sounds like my exact problem, I'm going to look through my library and see if there is a corrupt file then try again
Hopefully that is the source of the issue and that'll be solved quickly. Good luck to ya
The default from for the new rc3 release doesn't work on my phone, constant reeboots and freezes, so I'm wondering what other kernels are compatible with it. Currently I'm using the v52 kernel by grooby(?) But is giving me occasional reboots for no apparent reason.
hettar said:
The default from for the new rc3 release doesn't work on my phone, constant reeboots and freezes, so I'm wondering what other kernels are compatible with it. Currently I'm using the v52 kernel by grooby(?) But is giving me occasional reboots for no apparent reason.
Click to expand...
Click to collapse
I had the same problem, rc3 with the onecosmic kernel did not work, I installed the fugumod kernel, works fine for me.
hettar said:
The default from for the new rc3 release doesn't work on my phone, constant reeboots and freezes, so I'm wondering what other kernels are compatible with it. Currently I'm using the v52 kernel by grooby(?) But is giving me occasional reboots for no apparent reason.
Click to expand...
Click to collapse
you need no other kernel. Just flash RC3 over your current installation. I had these freezes and reboots too. after flashing RC3 and wiping cache/dalvik-cache about 4 times ICS seems to running stable and fast now.
Give it a try
I tried it many times, about a dozen or so. I don't think my phone likes the lower voltages the kernel uses by default. It only booted one in three times and when it did boot it never let me finish the setup screens before freezing.
@ regarding the fugumod one does flashing that one reintroduce the media storage bug? That was driving me crazy
hettar said:
I tried it many times, about a dozen or so. I don't think my phone likes the lower voltages the kernel uses by default. It only booted one in three times and when it did boot it never let me finish the setup screens before freezing.
@ regarding the fugumod one does flashing that one reintroduce the media storage bug? That was driving me crazy
Click to expand...
Click to collapse
I'm sorry that this didn't worked for you.
The media storage bug is still there even with the platypus kernel. So I think it's not kernel related.
Ahh thanks, I hadn't seen the bug since upgrading, but I don't think I had rebooted the phone since I got a working install. I tried a reboot just now and the problem showed up. Think I'll give the fugumod kernel a try.
Hello Guys!
I have a strange problem since i'm on ICS. When i turn on Wi-Fi, the toggle goes on and off! it's going crazy. I tried multiple ICS rom's. wiped my phone multiple times. But when i'm in cm7, i do not have this problem!. Does someone know, how i can resolve this problem? i know all the ICS roms out there on the thread have working wi-fi, but i can't get it done
Please help me!
Gr. Rutger
B_sHorTy said:
Hello Guys!
I have a strange problem since i'm on ICS. When i turn on Wi-Fi, the toggle goes on and off! it's going crazy. I tried multiple ICS rom's. wiped my phone multiple times. But when i'm in cm7, i do not have this problem!. Does someone know, how i can resolve this problem? i know all the ICS roms out there on the thread have working wi-fi, but i can't get it done
Please help me!
Gr. Rutger
Click to expand...
Click to collapse
Make a clean flash. Wipe all, install rom, reboot, wipe cache , dalvik cache, flash new kernel. Maybe left some settings from older roms or kernels
Sent from Galaxy S ICS
martynas900 said:
Make a clean flash. Wipe all, install rom, reboot, wipe cache , dalvik cache, flash new kernel. Maybe left some settings from older roms or kernels
Sent from Galaxy S ICS
Click to expand...
Click to collapse
thanks for your answer!, but i tried all those steps. But with no succes
Strange part of the story is, that wi-fi allways worked on my phone, also with ICS, but with newer versions or something, it goes wrong
For what it is worth - I also had the wifi toggling problem on the last 2 ROMS that I tried:
Slim_ICS_sgs_2.6.zip
aokp_galaxysmtd_build-25-be18.zip
The problems started exactly a week ago.
I ended moving back to Slim_ICS_2.5.zip where everything works OK.
From what I understand the problem is limited to a small number of users...
I am wondering if it might not be related to recent changes in the source code (both of the above ROMS are compiled from source).
I am however very curious why some people are impacted (with the wifi toggling issue) and others are not. Maybe it is related to their LOCALs (mine is FR/fr) and/or regions... just a thought. All comments welcome!
The problem line is that I am going to sit on the fence for awhile and see if something needs to (or will) be changed at source level.
@+