Temperamental... - G1 General

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.

Related

MAJOR problem - phone restarting every 10 seconds!

Hi guys,
this is my first time using these forums and I wouldn't have done that if the problem was easily solvable. However, this is a major problem for me and I couldn't find a thread nor a solution to it, so I'll post it here.
I have the i9305 4G version of the S3. I have had it for about a month now, and it worked fine, up until now. The phone suddenly starts to restart itself (not reboot!) for about 10 seconds, then goes back to the dashboard.
The problem seems to be the WiFi. Right after I get the "Connected to ... network" message on the bottom of the screen, the phone vibrates immensely once, then everything freezes for a few seconds, then another 2-3 vibrations, before the Samsung logo comes up with the LED light on. After a few seconds again I'm back in the dashboard until I get the "Connected to ..." message, and so on the process repeats itself.
Turning off WiFi seems to solve the issue, but once I turn it on again the problem reoccurs.
Something else I've noticed is that if I have WiFi turned off and cellular data network (for instance 4G) turned on, the "4G", "H+" etc. logo does not appear, even though I'm connected to cellular data! Don't know if it can be related to my main problem.
I have tried everything I'm aware of. Unplugging the battery, factory reset and back up, hard reset, wipe cache pertition. After the factory reset I can use WiFi again, but only for a few hours until the problem reoccured. I THINK once my battery is fully charged the problem occurs.
Note: I haven't even touched stock ROM, kernel etc. Nothing is flashed. Phone is in the same condition as when it came out of the box. Android version: JB 4.1.1
I would be forever grateful if you could help me out here, I can't have a phone restarting itself and vibrating like crazy every 10-15 seconds.
(Sorry in advance if this was the wrong place for this thread.)
- Payam
UPDATE:
Seems like my issue isn't just related to Wifi. Cellular data network was actually related to my issue, as I first feared. If Wifi is turned off and cellular data turned on, the same thing happens. Seems like the issue occurs every time I try to use the internet either way.
Anyhow, if I let the phone reboot itself without turning on or off anything at all, it will reboot about 5 times until either Wifi or cellular doesn't work anymore even though the status bar tells me that it is turned on!
This seems to be a serious connectivity issue and for the first time I'm suspecting interference with the phone's wireless network hardware. If none of you are able to provider an answer, I guess I have no choice but to hand it in to get it repaired or replaced.
Still noone who has a solution to my problem?
Payam93 said:
Still noone who has a solution to my problem?
Click to expand...
Click to collapse
My solution to your problem would be to just bring it to whoever you bought it from and demand a replacement. That isn't normal behaviour.
you can boot into recovery and do a factory reset and cache wipe
if wiping does not solve your problem, just return your phone.
I don't know if this is related, but, I had this issue once (the cause is not wifi though), and samsung fixed (or replaced) my phone.
Sent from my GT-I9300 using xda app-developers app
I'd wipe the phone and return it. This is not normal behaviour and should fall under warranty... Wiping might fix but this may happen again if there is an inherent problem with your handset....

HELP REQ - Stock Lollipop Note 3 N9005 - Random Reboots/Wifi-BT Clashes

Hi all,
Having a problem here.
Had my N9005 for about 18 months, never really had any problems with it - or rather, never really required anything of it which might manifest any problems.
I've always used Stock ROM's, soft-rooted.
Never triggered KNOX.
I'm currently running Stock Lollipop (latest Switzerland Open). Everything I'm about to elaborate is also the same using Stock Lollipop (latest UK Open).
I'm rooted on Lollipop using the method compiled by The TAMAS on XDADEV.
I root because my phone is work-critical, and so I use Titanium Backup to keep my data/calls/APN/SMS backed up and to make restoring easy, as well as to disable stock bloatware etc.
The problem may have pre-existed in pre-Lollipop ROM's, but the sequence of changes which caused it to be manifested included my need to update to Lollipop, about 5/6 months back.
THE PROBLEM - First and foremost, the damn phone reboots randomly. I become aware of it because it will vibrate for startup and play the Samsung startup tone and splash screen before booting to normal functionality. It can do this day or night, maybe 3-4 times a day. I have no error messages or warnings, it's done it while in my hand, while plugged in charging, while out and about, in the car, on wifi, on data. MOST times it reboots. SOME times it just shuts off and I don't realise it's off until I go to use it, or get a call on a second phone to ask why I'm not responding to calls or messages.
When it reboots itself, if I go to the Samsung Battery control panel pane and take a look at the battery chart it will show a gap which is longer than the time it took to reboot, and a shift in the battery meter level.
But, that's not the only possible symptom or problem with the phone.
I've noticed also that my WIFI does a lot of crapping out, or slowing to a crawl, even on my home AP. I've reset AP's, reset networks, reset the phone, forgotten and then reattached the AP in WiFi Settings. So I downloaded the Ookla Speedtest App, to see this issue in black and white, and sure enough, even though any other Android or iOS or Windows or OSX device in my place can connect via Wireless AP to my fibre connection and get great consistent throughput, the Note 3 can often appear crippled...
At it's best, it responds to ping quickly on the Speedtest app, and leaps up to the 30-40Mbps range with consistency for download, and up to 17-20Mbps for upload. This is the least I would expect it to do, my target standard.
At it's worst (which can be 'most of the time') it responds slowly to ping, and either struggles to get over 250Kbps download and maybe a crazy Meg or two for upload, consistently, a slow grind; or it may oscillate extremely wildly between slow and high speeds before eventually settling to unacceptably low transfer rates.
Up to press, I've been trying to chase these problems in isolation, believing them to be unconnected.
No success.
I've reflashed several times. I've Factory Reset. I've wiped data and cache. I've reinstalled and restored from Titanium. I've reinstalled and restored nothing but my SMS's and Call Logs. I've reduced my installed apps to bare minimums. I've tried it with a MicroSD installed, and without. I've bought another battery and replaced it. I've tried it in its case and without its case.
Then I started thinking that the problems were all the same thing, and stemming from the same root.
It suddenly occurred to me that my use of the phone changed significantly at the same time as I moved to Lollipop.
I need to be on Lollipop because apps and hardware that are critical to me are Lollipop dependent.
All at the same time, I began using a Moto360, a Bluetooth Receipt Printer and a Bluetooth Credit Card Reader, all of which are deficient in functionality or in some way hamstrung by not using Lollipop.
So I had gone from occasional BT user (maybe PlayerPro plus a BT link to headphones or my stereo occasionally; when needed, BT speakerphone in car) who usually turned BT off manually to preserve battery life, to a constantly connected BT user...
So I went back to Speedtest app, and tried to test the WIFI connection again. Sure enough, it was pitiful. Then I simply disabled BT on the N9005 and ran the test again, and had full 'through the roof' speed ratings.
I've tried this back and forth hundreds of times now, and it is predictable and established. BT is somehow crippling WIFI on my N9005.
I've tried running the phone on either wifi or data only, with BT off, and had a couple of days use at a time without any restarts. Put BT back on permanently, and the restarts resume within hours.
I'll be honest, I've even been cursing and swearing at my BT devices, because BT sometimes struggles to even maintain a continuous connection. I get vibrations all the time on my Moto360 indicating that the phone, which is on my person, has disconnected from the watch again, perhaps just for moments, sometimes for minutes, resulting in the watch eating battery life, trying to get reconnected.
I'm convinced now that all these things are related, and the problem lies somewhere in the interaction between BT and WIFI in my N9005.
It seems likely that I never noticed the problem before because I never required continuous BT connection before the point where I installed Lollipop.
Downgrading the ROM isn't an option. Leaving BT off isn't an option (nor should they have to be, on an 18 month old £600 smartphone).
Does anyone else have experience of this? Has anyone else had problems that they now suspect might be this same problem? Does anyone understand what's going on hardware/software wise, or have experience of a solution to these issues?
I'd appreciate your input urgently, even if only to affirm that I need to go to the inconvenience of temporarily buying another phone to replace this, while I send this away for a warranty repair.
Is this even a recognised hardware fault, or would I just get back an identical unit which is crippled from being able to perform as I expect it?
Please help.

Phone won't stop vibrating...

Posting here to see if more exposure would help.
Was wondering if anyone has run into this problem?
The phone was fine, rooted and everything, for a month give or take. Then all of a sudden, today, it started acting weird.
It was fine in the morning and everything, was able to use wifi, check emails, and stuff.
Then BAM, I tried to make a call, it didn't go through for the first 20 seconds or so. Then connected and a message kept popping up saying Phone is stopped or something during and after the call.
So, I restarted the phone. It restarted fine and everything, got past the 2 Samsung screens. Then hit the T-Mobile screen. and has been stuck on the T-Mobile screen for ~30 minutes now and just keeps vibrating.
It's getting quite hot, both front and back.
Any advice? Stupid Samsung making this a closed system so can't pull out the battery.
Can't even turn the phone off, only able to get to Download screen.
Weird problem.
Is there any way to pull the data and stuff off the phone at this point?
I'm thinking of going the factory reset route and do that to see what happens and see if it will fix the problem. It would probably not retain root am I correct and I would have to re-root again?
I could get into download mode and recovery fine.
I have had this issue on both at&t and t-mobile firmwares, but only while rooted.
Best thing to do is to re-flash the stock firmware again(or go to a different firmware if you'd like) but this is the reason I'm currently avoiding root. It soft bricks about a month in and is an easy fix but its annoying.
Was wondering about that too (flashing the stock firmware). But, will it wipe everything I had on there? Will any of my txt msg's and photo's or summat be lost to the ether?
Stupid question, I know, but had to be asked.
Thinking about flashing stock firmware and rooting agin for the sake of being able to do it again lol.
Well, if you flash stock, it does factory reset. That's why I have backups lol all I have to do is log into my Google account and everything is there.
buntobo said:
Posting here to see if more exposure would help.
Was wondering if anyone has run into this problem?
The phone was fine, rooted and everything, for a month give or take. Then all of a sudden, today, it started acting weird.
It was fine in the morning and everything, was able to use wifi, check emails, and stuff.
Then BAM, I tried to make a call, it didn't go through for the first 20 seconds or so. Then connected and a message kept popping up saying Phone is stopped or something during and after the call.
So, I restarted the phone. It restarted fine and everything, got past the 2 Samsung screens. Then hit the T-Mobile screen. and has been stuck on the T-Mobile screen for ~30 minutes now and just keeps vibrating.
It's getting quite hot, both front and back.
Any advice? Stupid Samsung making this a closed system so can't pull out the battery.
Can't even turn the phone off, only able to get to Download screen.
Weird problem.
Is there any way to pull the data and stuff off the phone at this point?
I'm thinking of going the factory reset route and do that to see what happens and see if it will fix the problem. It would probably not retain root am I correct and I would have to re-root again?
I could get into download mode and recovery fine.
Click to expand...
Click to collapse
Did you have security log or security update disabled as that updates and causes weird after affects.
buntobo said:
Posting here to see if more exposure would help.
Was wondering if anyone has run into this problem?
The phone was fine, rooted and everything, for a month give or take. Then all of a sudden, today, it started acting weird.
It was fine in the morning and everything, was able to use wifi, check emails, and stuff.
Then BAM, I tried to make a call, it didn't go through for the first 20 seconds or so. Then connected and a message kept popping up saying Phone is stopped or something during and after the call.
So, I restarted the phone. It restarted fine and everything, got past the 2 Samsung screens. Then hit the T-Mobile screen. and has been stuck on the T-Mobile screen for ~30 minutes now and just keeps vibrating.
It's getting quite hot, both front and back.
Any advice? Stupid Samsung making this a closed system so can't pull out the battery.
Can't even turn the phone off, only able to get to Download screen.
Weird problem.
Is there any way to pull the data and stuff off the phone at this point?
I'm thinking of going the factory reset route and do that to see what happens and see if it will fix the problem. It would probably not retain root am I correct and I would have to re-root again?
I could get into download mode and recovery fine.
Click to expand...
Click to collapse
These two threads describe exactly your issue and solution - http://forum.xda-developers.com/verizon-s7-edge/help/g930t-updates-unroots-overnight-t3426636 and http://forum.xda-developers.com/tmobile-s7-edge/help/rooted-weeks-rebooted-stuck-t-mobile-t3425814
I had the same problem, twice I had a rooted device totally lock up and had to re-do everything. But after disabling the security updates as advised, I'm currently going on two months without a problem.
Hope this helps!

Bootlooping, Bluetooth issues, what do I do?

I've enjoyed this phone the entire time I've had it but in the last ~6 months it's gotten less and less reliable, to the point that it crashes and restarts itself randomly at least twice a day.
To be clear, this phone was unrooted, locked and on stock firmware when the first symptoms appeared. The first symptoms were that it would fail to connect to bluetooth in my car about once every 10 times. That became more and more frequent, then it would randomly FORGET all my bluetooth pairings and it would work for a while then progress in the same manner.
More recently it would start rebooting itself (when I wasn't even doing anything -- it would just be sitting on my desk and reboot) -- and now it has started to do this but get stuck in a boot loop.
So I figured I would take the plunge and try a new rom if everything else failed. I installed Lineage OS and so far everything has been good, but now twice it's crashed, rebooted, and been stuck in a bootloop and had to be factory reset *again*.
Is this phone just defective or is there something I can do to fix this?
Sounds like a defective eMMC chip... Not common, but hardly unheard of.
You can try going back to stock, performing a full factory reset, and add nothing but essential apps.
Otherwise, without a realtime logcat of the reboot to determine the cause, it's all speculation.

Help - Random Reboot Problem

This is an ongoing, intermittent and devastating problem I have. My phone will be working perfectly fine, then all of a sudden it will randomly reboot. Then it will work for a few minutes or hours, then randomly reboot again. Then for a shorter time and reboot again until the phone basically can't even get through the bootup process without rebooting. It will be essentially bricked for anywhere from 1/2 a day to nearly a week (though it usually manages to get to working for 15 minutes at a time for most of the week. Then, all of a sudden and for no reason I can tell, it will just start working fine again for anywhere from several days to a month. This has been going on for at least 6 months.
It reboots during any manner of activities with the most common being phone calls, texting (I usually use Handcent Next SMS), anything with the keyboard (stock), browsing, swiping on the home screen, etc.. Really anything causes it, including it just sleeping with the screen off. The same problem occurs when in Safe mode, with or without the SD card (using as just extra storage, not phone memory), and with or without the SIM. It doesn't matter if it's plugged in or not. I have noticed what seems to be a greater tendency for rebooting to occur when the battery is low.
I am on T-Mobile (if that matters in any way for OTAs and such) and running the stock ROM without root. I'm about to try a factory reset but that has not been a permanent solution in the past.
so I just did the factory reset and it rebooted during the initial phone info setup (select your language, etc.)... I think it's toast... Does anyone know if this is the sort of thing that can be repaired for <$100 or should I just buy a new phone from ebay?

Categories

Resources