Does anyone else have this problem? - G1 Q&A, Help & Troubleshooting

For at least the last 6 months, from about the time I installed JF 1.5, I suffer from kernal panics and reboots when I either carry the phone in my pants pocket, or sometimes when i just set the phone down on a hard surface. In the pocket, perhaps the buttons are getting all mashed up? A short? Don't know. Setting it down, something jars phone or some sensor. ... Finally ready to deal with this.
Anyone else have this problem? I'm now running CM 4.1.11.1 and have had a few wipes in past months. Hardware or software?
Thx.

gimiento said:
For at least the last 6 months, from about the time I installed JF 1.5, I suffer from kernal panics and reboots when I either carry the phone in my pants pocket, or sometimes when i just set the phone down on a hard surface. In the pocket, perhaps the buttons are getting all mashed up? A short? Don't know. Setting it down, something jars phone or some sensor. ... Finally ready to deal with this.
Anyone else have this problem? I'm now running CM 4.1.11.1 and have had a few wipes in past months. Hardware or software?
Thx.
Click to expand...
Click to collapse
It might be hardware because noone else is having those problems

May have solved my problem, sure seems like it.
I upgraded apps partition to ext3 last night, from ext2, in order to run CM 4.1.999, and all seems well and done. (And 4.1.999 is blazing fast.) Guess something was corrupted and causing kernel panics and reboots in strange situations. .... Or my phone is afraid of the dark.

Related

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?

phone shuts off!!! help..

Can someone please help me..
I installed Cyanogen 3.4 when it got released a few days ago and it was running smoothly.. I think he is a genious. Just today my phone shut off on its own and I had to take the battery out and put it back in to get it to come back on. I don't know if it is Cyanogen or some sort of app, as I download apps quiet frequently. I am going to go through my apps now and also reinstall Cyanogen 3.4 tonight and leave my phone on all night. I guess I will have to see in the morning..
Anyways, can someone help
I ve fot sometimes the same issue with dudes cupcake which use th cygnonen kernel...
I ll be glad to have a fix
Are you overclocking the processor? That might contribute to it shutting down.
I do overclock but why do i have to 'battery pull' to make it reboot?
Yes, same issue here.
Uhh, again...
Powered up, set to standby, waited 1 min, shut down.
EDIT: I'm on Rogers Cyanigenized.
Same issue here. Complete lockup with screen off, have to pull battery to boot again. Seems to happen every 6-12 hours for me.
My Phone:
Cyanogen 3.4
radio 2.22.19.26I
Haykuro's SPL
Kernel 2.6.27.24-cm by [email protected] )
NOT overclocked, and no clocking tools even installed. Persists after several clean wipe and reflash also.
This thread's timing is great... I was just about to reset back to rc29 and build back up. Thought I was going to have to replace my phone
Rastasia said:
I do overclock but why do i have to 'battery pull' to make it reboot?
Click to expand...
Click to collapse
This question should probably be in the Dream section and will probably get locked/moved but Pulling the battery reset the "overclock" until it boots back up. This would be why pulling the battery helps.
hey you don't havbe to pull battery just push end call start call and menu all at once it will reboot you phone
Ok, thanks to Jakob, we know, that android freezes, is doesn't shut down.
I now tested with and without overclock, it made no matter to me not to overclock, there's no difference.
But I experienced it didn't happen when it's connected to a charger..
mysterious..
This keeps hapening to me, first it was happening in Cyanogized Rogers rom, then in The Dudes 1.3 b 12, I'm flashing JAC1.62 right now, this never happened to me before I got my class 6 16gb and started using apps2sd
Just curious, does this happen to anyone without a2sd
i'm having the same problem
seems to happen in the builds using the Cyanogen kernel. I'm sure this issue will iron itself out in future releases so just sit tight.
I too am having the problem on the Cyanogen 3.4 build. Its definately a change in 3.4 as I didn't have this problem in any of the 3.3 betas. I'm doing Apps2SD as well.
One thing I have noticed as well is that networking has been acting flakier than normal.
I had this issue on the pre-cupcake radio but not as frequent, so maybe it's just an amplified version of the same problem? There was a thread about it before but I'm too lazy to search for it.
The hangs was the only reason I moved to virtududes rogers rom v3
I'm going to try and get this sorted out tomorrow. For some reason the OOM killer kicks in sometimes and kills a critical process like zygote.
atleast you don't have this problem!
I've reflashed,wiped,formatted and apps2sd2 or sdpsplit, so many times already... trying different ways for each. But same thing always happens... my memory card gets damaged then wiped all by itself.
Uninstall toggle Setting and use Reparing Ext partition with Cyonagen recovery seems to fix this issue
So happy I found this thread! I'm using Google Ion and having this issue since yesterday. So annoying. Anyone got a fix?
I`m having the same problem, the phone freeze, looks like is a hardware problem, i`m on CRC1
I have started to have this issue as well. I am currently running Cyan4.1.999. It happened yesterday while on a call, after a call, and also while the phone was on charge.
Solutions?

A little help please?

Okay, so I had installed the modified mms.apk on cyans 3.9.7 I believe it was and it was all good until my phone rebooted itself. After it rebooted I was having issues with the touchscreen where it wasn't picking up my finger.
So I wiped, installed Cyans 3.9.10, but as soon as it loaded up I still had the touchscreen issue. Now sometimes it picks up my touch but doesn't exactly know where my finger is and the screen starts spazzing out. The only way I can use the phone is with the trackball...
Has anyone had this issue/know how to fix it? Any help would be appreciated.
Rayman0625 said:
Okay, so I had installed the modified mms.apk on cyans 3.9.7 I believe it was and it was all good until my phone rebooted itself. After it rebooted I was having issues with the touchscreen where it wasn't picking up my finger.
So I wiped, installed Cyans 3.9.10, but as soon as it loaded up I still had the touchscreen issue. Now sometimes it picks up my touch but doesn't exactly know where my finger is and the screen starts spazzing out. The only way I can use the phone is with the trackball...
Has anyone had this issue/know how to fix it? Any help would be appreciated.
Click to expand...
Click to collapse
the g1 is known to have touchscreen issues.
so it might just be a hardware issue.
have you applied the fix permissions script?
that miiiight help hehe.
also, you could of been more specific with the title of this thread
Fix_permissions didn't work, I even tried wiping my ext partition.
I probably should have been more specific, but I'm tired (3 hours sleep), annoyed and pissed off.
Rayman0625 said:
Fix_permissions didn't work, I even tried wiping my ext partition.
I probably should have been more specific, but I'm tired (3 hours sleep), annoyed and pissed off.
Click to expand...
Click to collapse
have you tried repairing the ext filesystems?
(assuming you have cyanogen's 1.4 recovery.
again it might just be a hardware issue and not rom related.
Yup, tried repairing the ext filesystems a couple times. I'm on the phone with T-Mobile right now, god this is such a pain hah.
Just got off the phone with Tmobile and I'm getting a rep. Thank you for your help Mrcrs. It was appreciated, thread over let it die.

Rom/phone problems ???

Im not sure if im posting in the right place, but i think my phone doesnt like CM roms. Ever since i switched from JF to CM 3.6.8, my phone is constantly freezing up, in wich i have to remove the battery and put it back in so i can use it again, or in some cases is very slow and sluggish. This is completly random, as no specific event triggers this behaviour. The phone has never been dropped and has never touched water. Right now im using CM 4.0.1 and i still get the same behavior and even removed the partitions from SD card leaving only the Fat32 partition, thinking that might be causing it. No themes are installed at the moment either, and have tried several times wiping/reflashing.
Anyone can point me to what could be causing this ?
skat325is said:
Im not sure if im posting in the right place, but i think my phone doesnt like CM roms. Ever since i switched from JF to CM 3.6.8, my phone is constantly freezing up, in wich i have to remove the battery and put it back in so i can use it again, or in some cases is very slow and sluggish. This is completly random, as no specific event triggers this behaviour. The phone has never been dropped and has never touched water. Right now im using CM 4.0.1 and i still get the same behavior and even removed the partitions from SD card leaving only the Fat32 partition, thinking that might be causing it. No themes are installed at the moment either, and have tried several times wiping/reflashing.
Anyone can point me to what could be causing this ?
Click to expand...
Click to collapse
I it might be a problem when you flashed try flashing older version of cyanogen and the flashing 4.0.1. again. Worth a shot

Touch Screen Issues

I have a stock N1, updated to Froyo. So every now and then, ever since I got the phone, the screen just stops responding when waking it up. Sometimes, the screen doesn't turn on at all, but the soft buttons light up. And the only way I've found to fix the problem is to either restart the phone, or connect it to my USB.
Was wondering if it's a hardware or software issue?
same thing happening to me aswell...seems to be only since Froyo flash. Really crappy when you are trying to show off the phone and you have to reboot first. Im gonna mess around a bit tonight and see if I figure anything out...Im also not getting any trackball notifications... I think its software related, for now.
I can say it's not Froyo since I've had this problem before the update, unfortunately.
mailliw320 said:
I can say it's not Froyo since I've had this problem before the update, unfortunately.
Click to expand...
Click to collapse
Ok some weird stuff going on for sure..
With CM 5.0.6 every couple days I would the keyboard would "uncalibrate", but the screen would never freeze up.
Since installing Froyo I am getting the freezing and unresponsive screen at least once a day.
Lets hope my it is not my screen getting worse. Ill have to flash back to CM 5.0.6 and see if I still get freezing.
Bye bye Froyo, see you in a couple days!!
So...anyone else with this issue pre-Froyo?
ive never had my nexus freeze, then i flashed froyo and that day it froze for about a minute, now it has done the hard sleep thing and it does it more times per day each subsequent day.
I know that we have an early "test" version of froyo so this stuff isnt grave, but since there seem to be groups of people experiencing different issues, i also wonder if its possible that specific apps can cause problems unrelated to the app since they arent really ready for froyo...is that possible and does anyone know of apps to beware of? not so much apps that dont work but apps that cause other problems?
Edit: my phone is stock by the way
i used to have a lot of problems when i switched from landscape to portrait mode with the calibrations but since ive put on 2.2 that problem is long gone and i have no other issues...
I had shocking touchscreen issues on 5.0.6, to the point where the phone was unusable and I had to reboot or pull the battery. Turning the screen off and on using power button would work occasionally but not always. Unfortunately I am still having the occasional problem on froyo. I had some mates trying to troubleshoot for me and took a few logs, the recurring error was (CM 5.0.6):
I/InputDevice( 117): Dropping bad point #1: newY=176 closestDy=3401 maxDy=2779
I haven't taken a log while on froyo
Thanks for the input, fellas. Sounds like it's a more apparent issue in this test release of Froyo. I've had the issue since before flashing the update, with stock 2.1, but it's sounding like it's software related and nothing actually wrong with my phone. Guess I won't bother contacting HTC haha

Categories

Resources