story so far:
never locked milestone 2 with 2.2.2, flashed by mistake with cm7 droid 2 update, successfully reverted to 2.2.2 with sbf then flashed with miui 2.5.25 but due to few force closes of launcher i decided to try cm7
all went ok and it was working perfect, but after 4-5 hours of configuring, i restarted it few times to check if all settings are kept intact, after one of the restarts all radio was gone, i had plane symbol on taskbar, but no way to turn airplane mode off, tried to restart it couple times, batery removed etc. but nothing helped
wiped it clean & flashed again with 2.2.2 sbf, then updated it to cm7 again,it was working fine in the evening, i left it on overnight, but there was no radio at all in the morning
so i took battery away for 15 minutes, restarted, and there is gsm\3g working ok, but no wifi at all
tried few reboots, took off battery, nothing changes
tried milestone 2 toolbox basebands 2.2 & 2.2.2 - nothing changes
then i tried wiping cache & user data from build in recovery (x+power on, @), that did the trick for now, as i have both gsm, wifi & gps back
any advices how to stop it from happening or at least track where the problem is?
full wipe helped, it seems ok now, working fine for 24 hours now
(next time i try just to delete remembered networks as someone suggested)
only thing that i have problems with is force close of com.bel.android.dspmanager within minutes\seconds from reboot (i guess it happens anytime when audio is switching (from media player to call etc.)) but i can live with that...
EDIT:
it just happened again, all radio gone after reboot, i restored with nandroid backup made this morning and it is working again...
i try to backup it first if it happen again so i could compare it and find what is going on...
ANOTHER EDIT:
36 hours later battery dropped to 0% (i did that intentionally - really heavy use) phone switched off, so i connected charger, turned it on and guess what - all radio gone again
this time removing battery for 30 seconds worked and it started without any problems...
i probably should shut up and start a blog, but im really curious why does that happen and why sometimes removing battery is enough and sometimes i have to restore nandroid backup...
last edit:
flashed stock 2.3.6, had to tweak voltage a bit but it is rock stable now, no complaints except for i being really slow (flash - youtube etc.) kinda like my old n900
Related
My G1 has recently started playing up. The problems first started with cyanogen 4.1.9999 - it would loose signal, but a reboot sorted this out and it may only happen once every two or three days if that. It was an unstable ROM, no biggy.
But then one day, after rebooting, it got stuck at the android screen then just turned itself off. This repeated several times before it just wouldn't turn on. I left it for a while and tried again later, it turns on, boots but no signal. Rebooting did nothing.
I reflashed (without wiping) cyanogen 4.1.999. and everything seems okay. But then the phone started crashing and rebooting rather a lot, and rather unpredictably. So I wiped, flashed the ADP rom and then cyanogen 4.2.1 rom. This process was a massive brainache - plugging in the usb cable managed to crash the phone within 2-5 min guaranteed, it automatically rebooted.
So here I am. Cyanogen 4.2.1 - after a complete sdcard format, wipe, ext3 repair and flash. The problems still persist! But it's temperamental, a lot of the time I loose signal still, it often reboots itself and hates anything plugged in the usb when it's turned on - making charging the thing awkward.
I used the log collector app to get these logs
http://nopaste.info/17b5351296.html
http://nopaste.info/2e98b9d044.html
At some point during those logs, the signal is lost. The log collector doesn't seem to retrieve a very long backlist, these were taken minutes apart but don't overlap, so I haven't caught a crash. I'm not sure if there are better ways to view logs/debug?
But it's all very temperamental. Occasionally it boots up and life is fine. But more often than not it will loose signal and reboot itself somewhere along the line.
Has anyone come across anything like this before? When it looses reception if I manually try an connect to a network it will say
"This SIM does not allow a connection to that network"
Click to expand...
Click to collapse
I've read that could perhaps be a problem with the sim... but the sim wouldn't cause reboots would it?
Any advise would be great. I bought the G1 off ebay just under a year ago, so no warranty.
my battery was running low, (and coz poor battery issues with JPY), i didnt notice when it switched of. normally i use the power button to turn the screen on to unlock, but instead i realised the phone had been off as it was now booting up...it booted up fine went into the homescreen and then vibrated once and powered down.......now it was powering down for a long time and occasionally there were vibrations and the lights on the home keys were constantly on. the screen was black. i got home and tried to charge it but the progress bar showed no progress on charging, i tried to switch it on but it would go to startup screen vibrate cupla times and power down. so eventually had to do a hard reset in recovery mode. tried every option but in the end had todo it by wiping data.
now the thing is, is this supposed to happen? if ur battery suddenly losses power ur whole fone will screw up?
for future ref if ur battery dies dont try to switch ur fone on until u got some charge in it and use the home key to put screen on..
Sounds like it could have been faulty firmware .
JPY does not have a significant battery drain problem per se .
jje
Black screen, vibrations and no boot after restart
Hello! I had almost the same experience (Black screen after reboot and occasional vibrations) only mine refused to boot even after memory wipe and after flashing new roms.
Was your phone rooted? Because I think rooting a 2.2.1 rom (XWJS3) was the beginning of my nightmare. keep in mind that the phone was working like charm for two months. This was the second time I had a problem. The first time the phone started after performing a factory reset by itself!
In case this happens to you next time and for every non experienced galaxy player (like me) reading this:
Don't panic! Blank screen, vibrations and no boot doesn't necessarily mean a hardware problem. Finally I managed to fix it flashing eclair and repartitioning with pit512. Now I'm a happy XWJS8 user
And a question for the experts: Any clue why this happened? Is it really a rooting issue? Can a cheap Chinese battery from ebay cause this?
everything was stock on mine, no root.......maybe thats why i could recover it??!!
Maybe! and I hope the reason is faulty firmware as JJEgan says. If this is true, your phone will be fixed by the next update.
I was very urge... the same happened again. It's been a month of smooth functioning and now after a simple restart, the device doesn't boot for absolutely no reason (Stuck on black screen constantly vibrating). Since my phone wasn't rooted, and I haven't seen many people talking about a problem like this I suspect:
1. Faulty hardware (for a few devices including yours and mine)
2. A Bad app.
Contacts Vanished
Hey Everyone
Im having similar problems, i updated my sgs to the js7 version of froyo, then rooted it with oneclick method. this was as i got the phone a month ago. Its been smooth sailing since then. But last night the phone powered down and wen it loaded up it had no contacts, my sms where still there but all the apps had a force close issue none worked. so cleared the cache in recovery. Still nothing so i did a factory reset and once loaded up. i formatted the sd and internal within the settings option. So the phone was now clean. I then connected to pc luckily had backups so installed titanium restored all my apps n settings. Using kies restored my contacts n thanks to an app called sms backup i restored those.
So all was well and worked again. I didnt restore the apps i had installed within the last week to make sure it was not a faulty app. I was happy, but now tonight it did it again. No contacts again.
Pls help
Any suggestions
That's exactly how it started for me. One month after rooting froyo 2.2.1 Suddenly everything force closes and the device hard resets by itself. I reinstall all the apps and then after one month and performing a simple restart, it refuses to boot. Stays in a black screen and vibrates every some seconds. I flash a new rom but does the same. Problem solved after repartitiong and flashing original eclair with pit 512. Reflashed a 2.2.1 rom and everything works perfect (the phone now is unrooted and with a nice clear stock rom). But then after one month again (!) I realise that some videos refuse to play. Trying to restart and craaash. black screen, vibrations and no boot. Did the same again (repartitioning and flashing) and now I wait for another month to pass and lose an hour of my life to do the same again. No idea why this is happening. Is it possible that rooting messes with something that stays faulty after restoring the file system? is there an app that we all installed and caused this mess? please this is the most serious problem I've red in this forum and still a mystery. I believe this thread should be sticky and we all share similar experiences because this looks completely random!
I believe this thread should be sticky and we all share similar experiences because this looks completely random![/QUOTE]
+ 1
Everything was fine until today when I decided to remove the stock recovery reload script, reodined CWM and also flashed the CRT off zip.
CapsLockKey said:
Everything was fine until today when I decided to remove the stock recovery reload script, reodined CWM and also flashed the CRT off zip.
Click to expand...
Click to collapse
Was the CRT script based on the EI22 framework?
I got it from the EI22 CRT off thread in the theme section.
Last night I also had an odd reboot. Not like the old random reboots that would happen when the phone was asleep, this one seemed like it was caused by a GPS crash. I had been using an app that triggered the GPS, (weatherbug I think) and when I closed it, the GPS icon stayed on. Even after I turned off GPS it still stayed on. The phone also started getting pretty warm. GPS itself no longer worked. After a few minutes of trying to shut down GPS the phone locked up. A minute later it did a "partial" reboot, playing the startup sound and eventually giving me the launcher screen. It was still not running right, with the GPS icon stuck on and the phone very sluggish. I did a shutdown and restart. The phone took a long time to start up, sitting on the "big S" for a while just like on it's first startup. Makes me think something got corrupted in the cache and it had to rebuild it.
I don't know if this was just a random event or the sign of problems to come.
This was on Stock EI22, installed as an OTA upgrade over a fresh EC05 install. The only mod was the CRT off / Circular battery mod that I created at the UOT kitchen.
Well fortunately my phone hasn't done it since. Thinking back, it may have been somehow triggered from a WiFi issue as I leave my WiFi toggle on most of the time and I had just pulled into my garage so the phone obviously was switching from 3G to WiFi around that time.
I am still having a weird issue though where Launcher Pro force closes initially every time I reboot the phone ever since then.
CapsLockKey said:
Well fortunately my phone hasn't done it since. Thinking back, it may have been somehow triggered from a WiFi issue as I leave my WiFi toggle on most of the time and I had just pulled into my garage so the phone obviously was switching from 3G to WiFi around that time.
I am still having a weird issue though where Launcher Pro force closes initially every time I reboot the phone ever since then.
Click to expand...
Click to collapse
Perhaps clearing data on LauncherPro and rebuilding the setup from scratch will solve that for you.
poit said:
Perhaps clearing data on LauncherPro and rebuilding the setup from scratch will solve that for you.
Click to expand...
Click to collapse
Tried clearing data, reinstalling, etc. Doesn't matter, still FC's immediately after reboot. Problem must be with Launcher Pro not liking something, because I just flashed CleanGB Rom (which includes the CRT-off and several other tweaks) to try it out and it does the same thing on that.
Update: Seem to have solved it, but not sure why. Had Voodoo Plus set to load module on boot, when I turned that off LP did just fine after rebooting. Decided to flip the load on boot back on to see if it would start FCing again and magically enough it hasn't.
I just had a random reboot and im in stock EI22..... Why?
Sent from my SPH-D700 using XDA App
Been on it since it was released, no reboots here... Working great for me.
ive had this off and on for a few days now. i find it to be caused by having multiple launcher in my case spb shell .had it running stock the first day so i flashed a rom and its still there. also other apps that use alot of resources will cause it. it partail reboots about 3 or 4 times and then runs normal.
CapsLockKey said:
I am still having a weird issue though where Launcher Pro force closes initially every time I reboot the phone ever since then.
Click to expand...
Click to collapse
I have the same issue with Zeam Launcher, clearing defaults doesn't seem to help. I wonder if there's some kind of half-assed check to make sure that TWLauncher is running? I dunno, but it's obnoxious considering how many times a day I'm forced to reboot EI22, added to the fact that they got rid of the deathgrip reboot.
My phone has "Randomly" rebooted on me several times, usually in an area with little signal coverage. Each time, it seems like there's some program (like Spotify or DI.FM) running that's making network calls when the signal craps out.
EI22 has been nothing but problems for me.
Just had my first random reboot. I'm stock EI22 not rooted yet. Imanually installed on the first day and this was my first. Phone was off just sittin on the table and the screen come on showing low battery but was still sittin at 30% and it shut off and the samsung screen come up and went thru the boot up process.
Sent from my SPH-D700 using xda premium
Please see this thread if you get random reboots with WIFI on.
http://forum.xda-developers.com/showthread.php?t=1359315
My Stable setting with no random reboots !!!!
After trying out virtually every rom/kernel out there (started with stock) I finally got a configuration in which I hadn't got any random reboot (or any other silly issues). My current setting are :
ROM : ERA Lagendary RC2
Kernel : Samurai 2.0.1 (inbuilt with Rc2)
Theme : Ei22Ics version 2 (just for fun !!!)
I have used Voltage control to OC it with settings : 400 Mhz minimum(recommended somewhere in dev post), 1340 Mhz maximum(~1400 mv voltage which I think maximum my handset can handle) with ONDEMAND governor.
My Epic is running flawlessly with no random eboots of FC's since last 4 days (while it used to reboot atleast 3-4 times daily earlier).
Hope this helps !!!!
Epic Timezzzzzzzzz !!!!!!
I still get random reboots in EI22, but not as many as I did on the GB leaks. I can cause a reboot by scrolling to fast in Settings, Applications, Manage Applications, All. I have had the phone run for 90 hours without a random reboot so I'm happy.
Had 2 reboots over the past week, where after charging all night I pulled the usb charger cable out and it rebooted. Stock EI22 except rooted, keyboard/CWM flash, and GPS_fix.
rando991 said:
Had 2 reboots over the past week, where after charging all night I pulled the usb charger cable out and it rebooted. Stock EI22 except rooted, keyboard/CWM flash, and GPS_fix.
Click to expand...
Click to collapse
Sounds like your USB port or charger cord is going bad. That is not random. If connections are shorted momentarily it will cause a reboot. Happened once to me on my cheap car charger.
Sent from my SPH-D700 using XDA App
i dont get any with
ROM = ASC AICS 5.5
Kernel : Samurai 2.0.6
Theme = Shake & Bake Mix Up v.5.9
kennyglass123 said:
Sounds like your USB port or charger cord is going bad. That is not random. If connections are shorted momentarily it will cause a reboot. Happened once to me on my cheap car charger.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Well I did notice it only happened on that particular charger (from Walmart)...also, my wife's epic didn't reboot, but had the charging light stuck on all day. I had to power it off and remove the battery to end it. Would that be maybe the same problem?
Been on CleanGB for quite a while. Went out of town this weekend to Chicago and ended up being rebootpalooza on my phone. Probably had almost half a dozen, once it just shut down in the middle of a phone call at the train station after the low battery notice came up, even though after I powered it back on it still had 28%. Another reboot was I unplugged the car charger shortly after the "full" indicator light came on. Others were just amazingly random. I've loved my Epic up until this trip when it turned into the most unreliable thing I've had.
I have had this problem with successive rom's (all cm7 based)
recently I wiped EVERYTHING and clean installed CM7 weekly 6 and for a few days it was all good, then the problem started again?
Tried to wipe cache ect (anything but a clean install) but still the same issue (PHONE WILL BE ON STAND-BY AND THE SCREEN WILL JUST TURN ITSELF ON/OFF ON ITS OWN??)
I haven't done a reinstall over weekly 6 because I am thinking the problem will just keep on coming back'
is there anything I can do? anything I need to show that will pinpoint the problem?
thanks in advance.
I would try a blur ROM first to make sure it isn't your phone. Then you can start thinking about hardware issues on the phone.
Sent with Tapatalk from my Blackberry Playbook
barry_ said:
I have had this problem with successive rom's (all cm7 based)
recently I wiped EVERYTHING and clean installed CM7 weekly 6 and for a few days it was all good, then the problem started again?
Tried to wipe cache ect (anything but a clean install) but still the same issue (PHONE WILL BE ON STAND-BY AND THE SCREEN WILL JUST TURN ITSELF ON/OFF ON ITS OWN??)
I haven't done a reinstall over weekly 6 because I am thinking the problem will just keep on coming back'
is there anything I can do? anything I need to show that will pinpoint the problem?
thanks in advance.
Click to expand...
Click to collapse
Very weird, but I noticed a similar problem the last few days. While at work, my phone goes into airplane mode(no reception in the building). When I was on CM7 neutrino, I had an instance where the phone drained the battery completely.
Recently I switched to cm9 Turl v8, and at work I pulled my phone out...the screen was on, Bluetooth was on and my battery had went from ~85% to ~20% mind you, I hadn't turned Bluetooth on.
A few days later I noticed I pulled my phone out and the screen was on...showed the screen and phone had been awake for a few hours....while in my pocket.
thanks for the replies
I got lucky i guess? I decided to start deleting recent apps/themes and the first few I deleted (themes for GOsms) stopped the screen turning on ect, no idea why but hey ho at least it stopped the fault.
Do not restore any thing after a fresh install of cm7 (complete wipe and clean before installation) and ull sure face no problems, i also had these problems not any more.
barry_ said:
I have had this problem with successive rom's (all cm7 based)
recently I wiped EVERYTHING and clean installed CM7 weekly 6 and for a few days it was all good, then the problem started again?
Tried to wipe cache ect (anything but a clean install) but still the same issue (PHONE WILL BE ON STAND-BY AND THE SCREEN WILL JUST TURN ITSELF ON/OFF ON ITS OWN??)
I haven't done a reinstall over weekly 6 because I am thinking the problem will just keep on coming back'
is there anything I can do? anything I need to show that will pinpoint the problem?
thanks in advance.
Click to expand...
Click to collapse
Hello lads! The last few days I have been trying to fix a huge problem with my Galaxy S4 i9505. I had been using the Google 4.4 rom for almost a month without any problem. One day, when my phone was low on battery it shutted down and I plugged it in my charger to power it on again. When it turned on I was prompted to the screen you see when you use the 4.4 rom for the first time. I had all my apps but everything was resetted. Every setting, all the app data, messages, etc. I thought this was a one time thing so I used about an hour to get everything back to normal again. Then the next day, same happened again. Phone turned off because of low battery, and everything was reset. I tried to google it but with no luck, so I did a factory reset and flashed the newest Google rom (4.4.2) with a new kernel called Ktoonsez. Got everything back to normal again and used my phone for a couple of hours before it just suddenly shutted down once again, but this time with almost full battery. When i tried to turn it on I was stuck on the Google loading animation and had to reflash 4.4.2. It turned back on and this time I decided to let the phone stay stock to see if any of my problems was caused of my apps or settings. It lasted for 2-3 days before the same thing happened again... I tried to flash different modems, other roms and firmwares but nothing have helped so far. I am also prompted with a message each time I turn the phone on which tells me that com.android.phone has stopped working. I have tried several factory resets, wiped dalvik, wiped cache, but still has the same problem... I have now given up trying and wonder if anyone of you know what I can do to fix the problem? Any tip is much appreciated and I hope to hear from you! Thanks!
Fredrik