Database Develop

Way, Way Too Many Reboots

Hola,
Dont know if Im over (ab)using my phone or if anyone else has the same issues.
My phone loves to reboot
-When I answer a call once in a while.
-When I turn off StreamFurious once in a while.
-When I disconnect the usb every once in a while.
-For no apparent reason every once in a while (ex. Ill find it turned off in my pocket or on my desk, but I never turned it off)
This happens about 3-5 times per day.
Also, on some of the StreamFurious reboots, it turns off and I have to pull the battery or it gets stuck on the G1 screen and never finishes.
Do you think I need a replacement or is this just a version 1 hardware thing?
Thanks in advance for your input!

We are going to need some more information to better assist you.
1) What Build are you using
2) Are you running Apps2SD
3) How much space do you have left on your internal storage?

Sure, thanks
Jf 1.5
Radio: 26I
No A2SD
31MB free
Nothing crazy.
I wipe every time I flash.
I've tried factory resetting too.
I try to keep the system clean.

he3 said:
Hola,
Dont know if Im over (ab)using my phone or if anyone else has the same issues.
My phone loves to reboot
-When I answer a call once in a while.
-When I turn off StreamFurious once in a while.
-When I disconnect the usb every once in a while.
-For no apparent reason every once in a while (ex. Ill find it turned off in my pocket or on my desk, but I never turned it off)
This happens about 3-5 times per day.
Also, on some of the StreamFurious reboots, it turns off and I have to pull the battery or it gets stuck on the G1 screen and never finishes.
Do you think I need a replacement or is this just a version 1 hardware thing?
Thanks in advance for your input!
Click to expand...
Click to collapse
Something like this happened to me about a month or more ago. It was everytime I try and use my phone when I was charging it, it would reboot. After a few days it would just do it at random. I just called tmobile and they just sent me a new one out.

the same thing is happening to me. my phone randomly crashes/reboots and i was starting to think it is the Haykuro build im using. is there any way to test the hardware? is there something like that in an app?

help
Are you using ahome or someting like that cause those programs cause problem with 1.5 uninstall all your theme apps if you have any

No, no themes.
Called t-mob, since I've had the device (sans insurance) less than a year, they are sending new hardware without a battery to replace mine. I decided to add insurance to the new hardware just incase. Thanks for the input! Glad I called!
Now to virginize the phone... heh

I have the same problem. There's a lot of this going around. It sure seems like a coincidence that it started with Cupcake for most all of us.

This has been something that has been happening since the RC33 load it...

Now I got the stupid random reboot problem. This is a warranty replacement and my first one never did this. I guess I gotta get another warranty replacement. Anyone find a definitive cause for this yet?

almost 100% sure you have a hardware problem

savethechicken said:
This has been something that has been happening since the RC33 load it...
Click to expand...
Click to collapse
I used to have the same issues WAAAY back after I recieved an OTA update from tmobile for rc33 or whichever one it was in march... back when I had still no idea what "cupcake" was...
always seemed to happen when I was:
answering a call, recieving a text while in a call that I started, etc.
but after I found out about the linux bit of my phone, I immediately cracked it... and... cupcake... and then? there weren't any reboots.... I wonder whats up with that? maybe something to do with OTA spls? I don't remember lol

rikupw said:
I used to have the same issues WAAAY back after I recieved an OTA update from tmobile for rc33 or whichever one it was in march... back when I had still no idea what "cupcake" was...
always seemed to happen when I was:
answering a call, recieving a text while in a call that I started, etc.
but after I found out about the linux bit of my phone, I immediately cracked it... and... cupcake... and then? there weren't any reboots.... I wonder whats up with that? maybe something to do with OTA spls? I don't remember lol
Click to expand...
Click to collapse
RC33 was the OTA was in March I believe maybe Feb. This didn't happen as much on RC30 and then RC33 came out and this started to happened more often. Obviously it is not the ROM doing it as not everyone has the problem but something seemed to trigger it on some devices.

alapapa said:
almost 100% sure you have a hardware problem
Click to expand...
Click to collapse
Going to have to agree. This is starting to seem like a Hardware problem, considering all the feedback we are being given.

I have the same exact problem.
It's definitely a hardware issue.
I was thinking it was because my extended battery pack is a little loose or some loose wiring. It happens when the phone is bumped a little. Like putting it on a table too roughly or flipping the screen up too quickly or it shaking in my pocket. Probably going to replace it.

I have this same problem...i had it originally with RC33 then it went away with the cupcake update and I recently root and install cynogen's build and its back to screw up my day
i don't think its a hardware thing ...at least in my case doesn't make sense to be gone for a month and then come right back after rooting

I also experience random reboot issue. Usually when the phone hang first then next thing you know, it is rebooting. Sometimes the phone will be just sitting there and it will reboot by itself. I always thought it is the ROM issue, never suspect hardware. I am running an old version of Dudes v1.3a build.

For me too
I am getting too many reboots too, just got a replacement phones(previous one did this too), same with this phone, first i thought it was Hardware but now it think its the roms. On hero it rebooted 3 times while booting the first time, on cyanogen it rebooted in a couple of hours, just dont know what the problem is, maybe abusing the phone

I got a replacement phone and still have reboots issue on it when booting, playing music etc.

charnsingh_online said:
I got a replacement phone and still have reboots issue on it when booting, playing music etc.
Click to expand...
Click to collapse
Makes me wonder on the apps your using in the background or settings you have up, or even the ROM. Do you have any extra info whats up before it reboots? Does it choke out due to low memory maybe?

my phone went fubar,but not bricked after flashing cyanogen 6.0..help!

Well heres the story. I flashed cyanogen 6.0 and all was great,fast,smooth,perfect... Then it all went downhill. The backlight cut out. After wiping,reflashing,doing everything possible as far as that it was still the same.
I soon figured out that if i lock my phone while it was closed, then slid it open and hit menu the backlight would turn on, but it will not work when its not slid open at all.
Problem #2
As i have been dealing with the first problem and i dont have alot of time to fix it because of work and all, it grew even worse. Now when i do what i was doing to get the backlight to come on, The phone will randomly freeze/backlight wont come on at all/ Screen wont even come on.
When i turn on the phone sometimes the screen wont even come on but the backlight will and it wont get anywhere."blank lit black screen no tmobile g1 logo"
This also happens when i go to recovery using home+power. I remedy that by taking out the battery and starting the phone till it works.
Could someone please help me out here i dont really have to much to spend on a new phone and it would be great if i can get this one going like it should again.

you need to wipe before reinstall
if you have armonR, you wipe everything the wipe menu and flash the rom and the flash gapp-3

ive done that many times, hasnt solved anything. i dont know whats going on..getting to the point where i might just break down and get a htc hd2 and put android on it

Try flashing the Defanged Base (which you can find on the cyanogen wiki) then flash the Rom again.

to be honest it was time for an upgrade anyways, now i have the samsung vibrant. Its awesome. Thank you for the help anyways though.

tank65 said:
to be honest it was time for an upgrade anyways, now i have the samsung vibrant. Its awesome. Thank you for the help anyways though.
Click to expand...
Click to collapse
You lucky f***! How are you liking it? I was thinking about getting one soon but i havent talked to anyone with one. Is there anything you dont like about it?

The four touch button lights won't go off when phone is turned off!

They just won't. They'll work normally when on and they'll go off after so much time of idling, but when I turn off the phone it buzzes like a complete shutdown and they just won't go off. I think it started when I loaded that leaked 2.3.3 captivate rom from SamFirmware and now it continues after a 2.1 stock downgrade and updating to 2.2 via Kies. I can't find anyone else with this problem.

hmm That's weird... if you pull the battery and replace it do they come back on?

Oh yea, I've been playing around with it and everything to see what I can do. It started happening about the same time my power/sleep button started messing up. It still is messed up, but I don't see how one would effect the other. Like I said, they work normally until I try to turn it off. Then, they don't go off until I pull the battery or boot it back up.

Jmurph3 said:
Oh yea, I've been playing around with it and everything to see what I can do. It started happening about the same time my power/sleep button started messing up. It still is messed up, but I don't see how one would effect the other. Like I said, they work normally until I try to turn it off. Then, they don't go off until I pull the battery or boot it back up.
Click to expand...
Click to collapse
if they dont go off when you turn it off until you pull the battery, it might be safe to assume your phone isnt actually off. Try reflashing whatever ROM you have going on within your cappy.

redkenji said:
if they dont go off when you turn it off until you pull the battery, it might be safe to assume your phone isnt actually off. Try reflashing whatever ROM you have going on within your cappy.
Click to expand...
Click to collapse
It has happened on two different ROMs. The 2.3.3 leak and then again when I flashed back to stock 2.1 and even after I updated to 2.2 via Kies mini.

maybe try calling samsung then. They may be able to address the issue. My friend has a vibrant that he bricked, hard bricked and they fixed it for free so, they might be able to help you out. it might be a hardware issue they can help you out with.

redkenji said:
maybe try calling samsung then. They may be able to address the issue. My friend has a vibrant that he bricked, hard bricked and they fixed it for free so, they might be able to help you out. it might be a hardware issue they can help you out with.
Click to expand...
Click to collapse
Very possible. I won't have a phone for that time, though. Haha....oh how we can't live without our mobile devices...

Att will send you a replacement first, then you send you old one back. If its still under warranty. I just told them I don't have a home phone, and they overnighted the replacement for free.
Sent from my Captivate running Continuum 5.6

Well, it randomly stopped. It shuts down and when it buzzes the backlights won't stay on. Idk what I've done for it to stop. I still have a busted power button, time to send in for a replacement.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App

Sliding won't work anymore

Hey guys,
I could need a bit of help! It's now the third time I'm having this problem, don't ask me why. I've got the feeling that I read the whole forum here, but didn't find anything similiar.
The 1st time I didn't change anything (ok, rooted it, but nothing else)
The 2nd time I overclocked it slightly (~850-900 MHz)
Now I'm using MIUI.
But back to the problem:
I'm unable to use the keyboard, every time I'm sliding open the keyboard (even when it's turned off), it "crashes". The screen stops working or it freezes, the only way to turn it off is taking out the battery.
However, the bigger problem comes now: I'm barely able to restart it. It tries booting, but is restarting all the time or the screen is just turning on (in some angles you see that it is turned on but it's black). After many retries, it starts working, sometimes the bootloop is running 15min or i have to manually restart it 10 times or more. The strange thing is that the keyboard works fine, nevertheless I have to choose between using it opened (taking it with me becomes difficult ) or closed...
...the main problem now is flashing a new Rom, I'm currently trying it through the android sdk and adb, but using the power-button + x is easier
I don't think that I can solve the problem, I sent the device two times back (warranty till may 2012), but maybe someone here knows a bit more. My guess is that one of the sensors is broken, or some parts of the display that should manage the sliding process...
Anyway, thanks for your attention!
Web

If you already have Rom Manager, just click Reboot into Recovery..

inches0 said:
If you already have Rom Manager, just click Reboot into Recovery..
Click to expand...
Click to collapse
Tried to use one a time ago, but it wasn't working right....
However, now I'm not even able to boot it, the screen just flashes and turns off itself before trying to restart a few moments later....guess I lost my Milestone

Sbf back to stock?

taptaptouch said:
Sbf back to stock?
Click to expand...
Click to collapse
the computer isn't finding it anymore...I'll back up the data and try use my warranty... I hope that they don't complain about MIUI...
But I'm still not getting the point, why my mobile had these issues three times, although they "repaired" it twice...and nobody else is having the same problem

Galaxy Mini reboots out of itself

Heya all,
So my Galaxy Mini started rebooting itself today.. Anybody knows what to do? I can't give much details only that I thought the problem could be the custom rom (CM7, New Experience). I flashed it back to stock, but it's still doing the same thing, sometimes it'll hold out for 30 minutes but sometimes it restarts and I can't even open Whatsapp before it reboots again.
All I can tell the on/off button for locking isn't always working as fast as it should. Could this button be stuck or something like that?
Also warranty is gone, got water damage from like 1.5 year ago.. Maybe that could still have something to do with it.
Thanks in advance,
Sanderth.
Update: I was just viewing a WhatsApp message and it rebooted itself again, please does somebody have any advice on how to fix this?

Bump: Please does anybody know what the problem could be? Today at school I wasn't even able to send a message via WhatsApp
Edit: I'm pretty sure it always happens a few seconds after I pressed the on/off button to lock. I just tried to lock it, got the prompt where you can enable airplane mode and turn the phone off and I clicked the back arrow, after ~5 secs it rebooted, could something be stuck behind this button or could my ROM be bugged?
Edit2: Well I disassembled my phone, probably something was stuck behind my button and fell out or something else was wrong with it.. But the most important thing is: It works like it should again, locking is going smooth now and it really feels as if my phone was better than before XD
Next time I'll open it first before opening a topic on xda, but well.. Hopefully somebody who will ever have the same problem will find this thread and fix it the same way I did

:thumbup:
Sent from my GT-I9300 using xda premium

Well to be honest, it'll stick to randomly rebooting itself once in a while, less than it was before disassembling and putting it back together again though (From 5 times in one hour to max. 3 on a day). But trying this could never mess something up (as long as you know what you are doing.) At least it's possible to use my phone normally again.
For the people that don't know how to disassemble, use this: http://www.formymobile.co.uk/s5570disassembly.php
Disassemble until you've got the battery compartment of, then just assemble again.