Related
Hey,
My AT&T rooted nexus one is still randomly rebooting if I use 3g data. I am in Costa Rica and the 3g is on the 850 band. I also have to add the apn "kolbi3g".
So basically I can use the phone for anything and it works great, but if I add the apn and start using the 3g heavily I will get a reboot, sometimes it will reboot vibrate 7 times and I have to pull the battery. I have tried 2.1 and 2.2 rooted and not also cyanogen 6 all the same problem.
If I do *#*#4636#*#* and select the wcdma only it runs the 3g better but reboots way more, sometimes the instant I place load on the connection. However if I select wcdma "unkown" the 3g works much better I can use it sometimes 30min at a time without a problem.
So any ideas what I could try? Is there a kernel that will up the volt's a bit just help stability? Or anything else I could try? Data roaming is off, I have tried both off and on, no difference that I can tell.
Thanks a lot this is driving me crazy! Just got this phone Sunday too sick to my stomach of the thought I spend $600 on this phone if I can't get 3g to work
How about radio image???
It is currently on baseband 4.06.00.12_7. Is there a more current radio?
I came across this multiple reboot issue on a (locked) Vodafone UK Nexus.
It booted into the OS (lockscreen) and as soon as data connected it looped back to the last couple seconds of the animated Nexus logo.... and again.... and again.
I powered down the unit (battery pull), booted into bootloader (voldown+power) and selected clear storage (voldown,voldown,power) then (volup) to confirm.
This deletes the user data and you have to sign in and set up the phone again but it certainly fixed the issue. My only guess is some user data became corrupt and the kernel panicked and forced a partial reboot.
Give it a try and lemme know.
Cabarnacus said:
I came across this multiple reboot issue on a (locked) Vodafone UK Nexus.
It booted into the OS (lockscreen) and as soon as data connected it looped back to the last couple seconds of the animated Nexus logo.... and again.... and again.
I powered down the unit (battery pull), booted into bootloader (voldown+power) and selected clear storage (voldown,voldown,power) then (volup) to confirm.
This deletes the user data and you have to sign in and set up the phone again but it certainly fixed the issue. My only guess is some user data became corrupt and the kernel panicked and forced a partial reboot.
Give it a try and lemme know.
Click to expand...
Click to collapse
Just did that (had the phone plugged into wall charger), and the second I got to the home screen it rebooted then vibrated like 6 or seven times. Seems to do it worse when it is plugged in. And now it won't even boot up even after pulling the battery, it vibrates 6-7 times.
I am really worried about this, any other ideas??? I will try anything! Thanks for the help
Update! Now the phone just reboot when I do anything period with it plugged in. Just like posted in another thread on this section!
Please any ideas I am very desperate and very sick to my stomach!
Hmmm very strange.
I'm aware from what you were saying on the other thread that you've got an unlocked bootloader and you're wondering what to do on the warranty front.
If you've really tried different combinations of stock and custom firmware and having the same issue I'm tempted to say its a hardware issue.
Many people have returned their unlocked phones with no comeback from HTC some have reported that they have noticed the unlocked bootloader and have issued a motherboard repair as part of the fix because of this.
Although im unsure of the additional cost (if any) i would definitely recommend going through the warranty repair route with HTC. They won't say no and send you back the same broken phone. And who knows, if its a confirmed hardware issue they may just replace it as a goodwill gesture.
Other than that I don't have any more ideas.
A nexus support thread has a popular answer referring to the clear storage fix.
http://www.google.de/support/forum/p/android/thread?tid=40f52d29e9c4177e&hl=en
Just make sure you are definitely clearing the storage FROM THE BOOTLOADER before calling HTC. It is the first thing they will make you do before accepting a return anyway.
Cabarnacus said:
Other than that I don't have any more ideas.
A nexus support thread has a popular answer referring to the clear storage fix.
http://www.google.de/support/forum/p/android/thread?tid=40f52d29e9c4177e&hl=en
Just make sure you are definitely clearing the storage FROM THE BOOTLOADER before calling HTC. It is the first thing they will make you do before accepting a return anyway.
Click to expand...
Click to collapse
Ok thank you so much sir. I am so glad to hear that I may still have a chance at getting it replaced! It was very fullish of me to unlock it, I know, it is just that I figured it was software and could be fixed by unlocking. It is going to cost me $$$ to get this to the States, but that is life. If I still can't get it to work I will call htc and let you know what they say
Little update here. I cleared storage again and just simply disabled data, I have been using the phone for a couple of hours on work without any problems. Next thong I am going yo yty is another friends 3g similar card and see if it still reboots on that sim, if it does then I am calling HTC.
Also still open to any other ideas you guys may have.
TL;DR: My phone is experiencing a very similar problem to the broken internal SD after Froyo update, except on eclair and is fixed (apparently temporarily) with a factory reset. I'm on Telus, bought the phone from somebody off craigslist and have a return receipt. What should I do?
So for the second time in a few days my Samsung Galaxy S (I9000M from bell, bought on craigslist running on telus) was having problems opening an app so I restarted it. (The first time Market would force close whenever I tried to open it, the second time it was Browser). After the app force closed a few times I did a restart. The first time I restarted it (when Market froze) it went to the lock screen, with the default background (it looked like my data was all wiped). After unlocking the screen, I got a perpetual series of force close messages. This happened each time. I had to do a factory reset and lost all my settings, photos, messages and everything (No backups, of course. Facepalm). Then today I pretty much had it back to the way it was before the reset, and Browser force closes repeatedly on opening. I restart the phone again and this time it only gets to the 'S' animation then goes black/restarts after the animation stops. The capacitive buttons sometimes light up. Similar to the issues from the Froyo update I think, except I didn't update to Froyo. I can get to the 3-button recovery screen and do system reset as well which seems to not help the froyo issue, I think. It's currently working but I'm not sure how long that will last. I'm not pleased about having a phone I have to re-setup every few days. (I'm actually pretty angry...)
Anyway, I have a "Mobile Device Repair and Return Receipt" from the seller from craigslist. It's still under warranty. Anybody else experience this? Can I take it to bell and have it fixed with the documentation I have? What would you suggest I do here?
All, having a weird issue. I was on the phone yesterday using an automated menu system and my phone restarted. No rhyme nor reason why. It did that repeatedly throughout the day. I tried flashing a new ROM version, Phoenix 6.0!!, with no luck. I tried a normal restart, power down and then up, running a virus scan, pulling the batter for 30 minutes and no difference. The phone continued to restart. I finally got fed up and my battery was almost dead so I turned the phone off.
The phone was off for probably 5 hours and I charged it while off. I restarted the phone and transferred all of my content off, expecting to Odin back to stock and reflash Phoenix. The phone seemed to be behaving so I left it alone and plugged it into the wall for the night.
I got up this morning and everything appeared to be good. Went to work and still no problems, phone had an uptime of over 12 hours. Which would be what I would expect. Had the phone on my desk and I noticed it had restarted. When I mean it restarted, it went back to the boot animation and then loaded to the android screen and performed media scan and all my apps loaded on the home screens and services started up.
I went back to Settings->About->Status and the uptime was 18 hours now. So even with the restart, the uptime was still counting. Needless to say, I'm at a lose. Can't isolate any event that causes this reset or any app. Could I have gotten something from the automated call system? Is something just weird. I had been running Phoenix 5.2 for a few weeks with now problems so I'm confused. Any suggestions would be appreciated. I will probably flash back to stock and start again but I'd like to isolate this problem if possible.
To the best of your knowledge, no apps were just added, our settings adjusted?
Either way I would odin flash master clear. May even run stock for a but to see if behavior stops
Sent from my Captivate using XDA Premium App
sounds like a problem with the infamous 850-1900mhz handoff....
if your signature is accurate, that modem you are using is 1900mhz only i believe....it doesnt support 850, so if you are in an area where its trying to hand off to 850, it will cause a soft reboot.....i have seen it a million times myself when playing with the first run of i9000 roms
Pirateghost said:
sounds like a problem with the infamous 850-1900mhz handoff....
if your signature is accurate, that modem you are using is 1900mhz only i believe....it doesnt support 850, so if you are in an area where its trying to hand off to 850, it will cause a soft reboot.....i have seen it a million times myself when playing with the first run of i9000 roms
Click to expand...
Click to collapse
Hmmm...I have been using an i9000 roms for a few months with no issues. The last modem I was using was I9000UJK4, I think? I don't know without flashing back, whatever came with Phoenix 5.2 ROM. I had zero problems. I only flashed to that modem/ROM, Phoenix 6.0, in an attempt to fix the soft reboot.
flash just the JK4 modem and i bet the soft reboots stop. what you have listed there is i believe a 1900mhz only modem....
Pirateghost said:
flash just the JK4 modem and i bet the soft reboots stop. what you have listed there is i believe a 1900mhz only modem....
Click to expand...
Click to collapse
I will try that, when I can find it to download but the problem started with the JK4 modem. I was running Phoenix 5.2 with a JK4 modem and only flashed to the new one in an attempt to wipe whatever was causing the data.
Flashing UGJK4 right now, I'll see if that fixes anything however I'm not super confident since the problem occurred originally with a JK4 modem.
Update: Rebooted once after modem flash. Going to wait for a bit and see what happens.
if that doesnt work, i would think its a problem with your hardware
Pirateghost said:
if that doesnt work, i would think its a problem with your hardware
Click to expand...
Click to collapse
If the modem switch doesn't work, I'm first going to flash to stock and master clear. If the problem goes away, I'll flash to Phoenix again. If the problem comes back, it'll have to be part of my SW. If the problem persists at stock, back to AT&T for a refurbished phone.
Update: Looks like things are pretty stable right now. I'm not super in-tune with how the modems work but is there a way to allow the JK4 modem to use 850 or 1900 speeds, like an auto setting that will choose the best one. I use SGS tools for secret codes so if its in there let me know. So far so good, thanks pirate.
Reviving an old thread because I am also having soft reboot issues.
Unlike the previous poster, I am not using an i9000 based kernel. I am running the latest leaked Gingerbread for the i897 (JK3), rooted via Fugu kernel swap method; the only other tweak to stock has been to freeze via TiBu the AT&T Tethering Manager. I am even using the stock launcher as I try to isolate what is causing this.
The phone goes through spells where it will soft reboot every 10 minutes or less, and then periods where it will go days where it is stable. I have had this issue with multiple versions of the 2.3.3 and 2.3.5 leaks and am nearing wits end figuring out the cause.
Before each flash (and I have flashed multiple times with different stock leaks) I am wiping data and cache via recovery (I do not have CWM installed), then restoring apps only via TiBu. I have tried to be judicious about what I reinstall, but have not been able to identify if there is a misbehaving one yet.
I suspect this is software and not hardware, since I had this problem on my first Cap and have already done one warranty exchange; the external SD card, though, is the same for both.
I've looked for kernel panic logs and have not seen any, and have yet to find a good way to trap what is causing this.
This is my work issued phone (does Exchange sync and has company policies sent to it), so I am loathe to go all the way to a custom ROM, even though I realize that I voided the warranty when I rooted and went to leaked ROMs.
Anyone have an ideas as to what could be causing this, how I can isolate the problem, and hopefully resolve it once and for all? Worst case, I could go back to Froyo until AT&T finally drops the promised Gingerbread update, but I had different issues with Froyo with Market updates not always finishing and apps on the SD card not always being recognized.
I'm not gonna BS anyone. I'm clueless!!
I lent my phone to a friend for a few days and he installed one of the ICS roms on it. A few days later I realized that it would no longer keep wifi active. Anytime I'd attempt to turn wifi on it would say error and time out.
I figured no biggie I'll just Odin back. So I Odin'd back to Eclair and still no wifi. Even worse... when I boot the phone it takes exactly 33 minutes to get past the "Galaxy S" screen. It isn't frozen as I can see the S throbbing.
Another symptom of my problems is that the haptic feedback is gone.
In recap, No wifi, no haptic and a loooong boot.
As I said earlier, the problems persist in stock form as well as CM7.
Any help would be greatly appreciated.
OK, The weirdness continues. I decided to try roms I've used in the past to see if anything changed. I started off with Andromeda 1.0. The boot time is now back to normal and I've regained haptic feedback.
Unfortunately I still don't have wifi. It'll now allow me to enable wifi and it'll attempt a scan but comes back with "unable to scan networks". I attempted to manually add multiple networks and get the error "unable to save the network" then wifi gets disabled.
I'm at a loss at this point so I'm hopeful someone can come through.
Antiph3d said:
OK, The weirdness continues. I decided to try roms I've used in the past to see if anything changed. I started off with Andromeda 1.0. The boot time is now back to normal and I've regained haptic feedback.
Unfortunately I still don't have wifi. It'll now allow me to enable wifi and it'll attempt a scan but comes back with "unable to scan networks". I attempted to manually add multiple networks and get the error "unable to save the network" then wifi gets disabled.
I'm at a loss at this point so I'm hopeful someone can come through.
Click to expand...
Click to collapse
When you Odin'd back to Stock, did you Master Clear too?
Thanks for the reply.
Yes, I did do a master clear. Internal SD has been wiped but the problems continue.
The haptic feedback and boot time return to normal when I flashed Andromeda 1.0 but go bad again when I go back to stock.
Just went back to stock and am waiting the 30 minutes for the phone to boot so I can do another master clear. Can't see the second finding any residual files that the first didn't get but you never know I guess.
I just noticed that my Bluetooth isn't working either.
Data and cell work just fine though.
so... latest recap...
Currently running Andromeda3. The phone boots just fine in a nice fast timeframe. Haptic feedback is working fine.
Wifi and Bluetooth are no go's. Just don't get it
I was on 5.9.904 with Eclipse 2.2 and flashed back to 5.9.902 and upgraded to 5.9.905 then installed Eclipse 3 for 5.9.905 and now my 4G sucks.
Keep in mind I'm in a solid 4G area where it never switches to 3G.
Sometimes the icon is blue and it works but most of the time its white and doesn't work.
I have to set my phone to airplane mode and back for it to work again and sometimes that doesn't work.
If I go back to 5.9.902 and upgrade to 5.9.904 will that change the radio back to the old version or not? If nothing works I'm just going to get a replacement of hopefully a new phone from Verizon.
Thanks
If you had better connection with .902 then just FXZ back to that and don't install the official update when it ask you to. That is why there are different FXZ files so that you have the option to use what is best for you.
I had better connection on 5.9.904.
I just don't know if radio updates are permanent or not.
Will going back to 904 fix it?
Wow I dropped data while typing this message.
I haven't upgraded to 905 yet, but I've been having all sorts of problems with 4g for the past 2 days. I'm on 904 and eclipse
Sent from my DROID BIONIC using Tapatalk 2
scottocs said:
I had better connection on 5.9.904.
I just don't know if radio updates are permanent or not.
Will going back to 904 fix it?
Wow I dropped data while typing this message.
Click to expand...
Click to collapse
Radio updates are not always permanent. If you are on 5.9.905 you can FXZ back to 5.9.902 (which will put in the 5.9.902 radios) and then go find the 5.9.904 update.zip, and flash that in stock recovery to get back on the 5.9.904 radios.
Im starting to think it is something wrong with Eclipse 3 because the connection on stock 5.9.905 is working fine.
Me too - I ran the OTA - didn't lose root (am running SafeStrap w/.902 Pathsaver). I first noted the problem while in Beverly Hills - normally a full 4G area with few problems save the occasional network problem.
My network weather settings would not refresh though 4G icon appeared in blue - Also email was silent for too long.
The problem again appeared when accessing The Market (Play). The phone responded with No Connection/Retry. The connection would not return despite going to A/P mode or switching between CDMA/LTE. Finally, I restarted and 4G returned for long enough to download an app and listen to a podcast on BeyondPod.
This weekend, while listening to BeyondPod - the stream just stops and will not restart until the phone is fully restarted (ON BUTTON with -+ volume pressed).
I will revert to 902 and try flashing 905 from the SD card tomorrow.
Will report results -
This seems to be fairly uncommon as such, I'm hoping that the above will restore.
From all I've read - 4G is supposed to be ENHANCED with .905.
C'est la vie.
I think that I am not in a hurry to get the .905 OTA.
with all the issues with the last couple of radio updates im sure they will push out another one soon to fix those issues lol. it's best just to stick to a stable radio version until confirmed issues are solved.
Amendment to original post
Lemmy Caution said:
Me too - I ran the OTA - didn't lose root (am running SafeStrap w/.902 Pathsaver). I first noted the problem while in Beverly Hills - normally a full 4G area with few problems save the occasional network problem.
My network weather settings would not refresh though 4G icon appeared in blue - Also email was silent for too long.
The problem again appeared when accessing The Market (Play). The phone responded with No Connection/Retry. The connection would not return despite going to A/P mode or switching between CDMA/LTE. Finally, I restarted and 4G returned for long enough to download an app and listen to a podcast on BeyondPod.
This weekend, while listening to BeyondPod - the stream just stops and will not restart until the phone is fully restarted (ON BUTTON with -+ volume pressed).
I will revert to 902 and try flashing 905 from the SD card tomorrow.
Will report results -
This seems to be fairly uncommon as such, I'm hoping that the above will restore.
From all I've read - 4G is supposed to be ENHANCED with .905.
C'est la vie.
Click to expand...
Click to collapse
On further troubleshooting - assumed that root was not broken. It seemed that all of my apps were working as they should but when I attempted a SafeStrap restart and restore my UnSafe installation, The SafeStrap prompts would not appear. So, I checked root -found that it was in fact broken so, I ran Voodoo, restored root, ReInstalled Safestrap Recovery from the app and, restored my unsafe system to .905.
Since it was the weekend, I haven't had much of a chance to test 4G but while I was at the gym, I did listen to some podcasts. Email seems to be pushing. Today (weekday) should give me ample opportunity to test the update.
Hopefully, the restore fixed the problem.
This entire thread Sounds like bad hardware our user error
Sent from my Xclipsed Bionic
I am in the same boat here. I took the .905 update last weekend and my 4g has been terrible since. It stays 'white' most of the time and when it is blue and I open an application it instantly turns back to white and I get no connectivity...does anyone have a suggestion? Also, I was rooted and had safestrap. After the update...I guess I am not sure if I have root anymore? a root check app says I do not but I was still able to reinstall safestrap apk and then boot into eclipse.
Thanks in advance
I think this is a network issue. With last couple of days, my LTE has been showing white and wont connect to network. I still have 5..9.902.
Sent From Droid-Bionic
Using Xparent Blue Tapatalk
My phone is 5.9.904. Does that mean I can't get the 905 update?
So is it the update or a network issue?
ronaldheld said:
So is it the update or a network issue?
Click to expand...
Click to collapse
On my personal use, I was trying to see if the MAX batt saver option had something to do with the data connecting. Since setting it on nighttime save, I havent had too much of an issue.
these are from the eclipse forum
I take no credit, but used them both (despite not having any data issues at all) and others claim these work:
A:
1. Power down
2. Remove the back cover, battery, SD card and SIM card.
3. Power back up, let the phone come all the way back up and tell you that you can only do "emergency calls only"
4. Power down
5. Reinstall SIM card, SD card, battery and back cover.
6. Power back on and let the phone boot normally.
B. in settings, Battery, Battery Mode, do not use "maximum battery saver". use nightime saver. (I use custom battery saver, which just slightly adjusts the nighttime hours).
no harm in trying these.
Link to 905
Anyone have a solid link to 905? The one DROIDMODDERX posted here (http://www.sendspace.com/file/xo8f4g) won't download to my phone. Not sure if it is my phone or the link. I can pull stuff off of Google Play all day long though.
Juroid said:
I think this is a network issue. With last couple of days, my LTE has been showing white and wont connect to network. I still have 5..9.902.
Sent From Droid-Bionic
Using Xparent Blue Tapatalk
Click to expand...
Click to collapse
x2 on network issue. I've noticed 4g issues many times lately on my phone and also on stock .902
Not network issues....the leaked .905 is flawed.
My wife and I did a test. I did t his because for the 3 days I used the leak I noticed white data drops happening a helluva lot.
We were in the same room standing less than a foot apart in the same house.
We hit the same app/icons on our bionics at the same time even.
I had the .905 leak....it went white 5 times for roughly 15-120 seconds each time in a 15 minute window.....my wife's stock .902? NEVER.
Nuff said...or not. lol