Database Develop

HELP XDA! Phone Reboot's if using 3g Data

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.

Continuous soft reboot

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.

[Q] LCD BLACK BUT STILL FUNCTIONAL BLIND, MAJOR KEYS still lit up

First of all running stock Droid 3 Rooted Flashed to cricket
with all the fixin's, Bootstrap, CMW, ... etc....
:edit ... Now with safestrap.
_________________________________________
I noticed after taking my phone out of my pocket while trying to turn it on from normal off screen while on that it wouldn't show up the light still indicated it was working I can even turn off the phone.
Taking the battery out and back in semi fixed this but only to the extent where when the phone is turned on the moto logo doesn't appear but the droid eye does.
whence at the booted screen if I were to let it go black it has a chance to not stay on unless I RIGHT after it boots unlock it and keep it lit,
(but)
the main problem I noticed was it really only did this after lets say I was typing or doing anything with the qwerty board open and perhaps I let the screen turn off after a minute,
when I try to wake it up it stays black. EVERY TIME like most of the time,
it has to do with the keyboard being open when the screen goes to sleep.
WHAT IS WRONG *pulls hair out*
_________________________________
I can't say when but I've looked everywhere
tried uninstalling every app but the essentials,
then restoring to my first restore which was after my first initial root.
Tried factory reset,
Tried flashing back to stock,
yeah I think this counts for as much as I've gone insane looking for an answer for.
I have been told this sounded like a software issue so all I'd need to do is re install like I did when flashing back to stock THIS MORNING.
____________________________________________________
I need help to identify somehow if this IS or IS NOT a software/hardware problem.
and an answer to help me fix this would be nice as well thank you.
I know I am supposed to be brief but putting in all that into google and into every forum I have delved just isn't going to put it the way it needs to be said.
______________________________________________________
______________________________________________________
Edit:
Ok so far since no one has said anything I have also reinstalled my old newest state, still giving me crap.
Then just did the newest update 5.7 blah and still it's happening.
I hypothesize it might be the flex ribbon cable maybe (but it really might not) I read from another phone it might be a capacitor but it might not.
Whatever is wrong the phone still is able to at times now 40/60% of the time work properly and wake normal but then again not.
__________________________________________
Right as of now I have put isc to see if this helps .......... .... to be continued or helped.
I'm back, well ics installed fine after the second time made it boot loop over and over.
-----------------------------------------------------------------------
I can receive calls now
but
no sms, mms, or internet.
(even though the network status settings are blank it's weird I can still receive calls, and send calls.)
since you can't restore the apn's with 3rd party I now have this NEW issue.
the phone goes unresponsive within cdma workshop and ##Program does not work.
I'd like some help in finding out now how to if it is possible yet to properly flash to cricket and or just change my apns and get into cdma as well as QPST.
__________________________________________
PLEASE I NEED HELP thank you
-3nJo1

Yeah, it does sound like a hardware problem. If nobody else can help you fix it, you'll need to reflash the latest OTA update (or revert to your safestrap nandroid), unroot it and restore all the system apps that you may have frozen/deleted, and hope that Verizon will replace it.

Thanks
necromanteion said:
Yeah, it does sound like a hardware problem. If nobody else can help you fix it, you'll need to reflash the latest OTA update (or revert to your safestrap nandroid), unroot it and restore all the system apps that you may have frozen/deleted, and hope that Verizon will replace it.
Click to expand...
Click to collapse
Thanks for your input.
(verizon wouldn't replace it since I baught it from someone else (legit) and I don't have verizon.
UNLESS you think if I had the previous owner take it into the store could they replace it? what steps would they take to see if it was rooted?
_______________________
I never unrooted it when I did allll of this
Do you think rerooting is soumething that I should have done before doing this?
Or most likely is this a flex ribbon cable thing ....
I just tried the diagnostic (leave keyboard open then turn the screen off and on thing)
it came on at least 3 times normal then it didn't either right after the 3rd try or upon closing the qwerty board ...
also do you have an answer at all for the ics portion of my problem?
THANK YOU
___________________________________________________________
EDIT!!!!!!!! Actually realized I did reroot after the sbf ota flash .....
so all things aside yehs I also did that any other solutions inquiries ...
ANYONE ELSE PLEASE HELP!

Another path to try down is Motorola - depending on the age of the phone, I believe there's a warranty through them.

stud beefpile said:
Another path to try down is Motorola - depending on the age of the phone, I believe there's a warranty through them.
Click to expand...
Click to collapse
Thanks,
well it is less than a year old I think, could I be able to get motorola to replace it when all I have is the phone no receipt or box ???
MORE HELP FROM ANYONE ELSE PLEASE

I bought my d3 off craigslist and the power button and n key weren't always working. I took it in to Verizon and had a new one in the mail 3 days later!
Sent from my XT862 using XDA App
Sorry didn't read the part about you being on cricket. Maybe you could make friends with someone that has d3 on verizon have them activate it and take it in for you.

3nJo1 said:
Thanks,
well it is less than a year old I think, could I be able to get motorola to replace it when all I have is the phone no receipt or box ???
MORE HELP FROM ANYONE ELSE PLEASE
Click to expand...
Click to collapse
I believe there is another apn type tool that the Cricket Android tools are using for their specific settings. You may have to search XDA a bit to see if anything shows up for othere phones on Cricket.
Sent from my DROID3 using XDA App

[Q] Have you guys fixed the ghost call issue..?

It seems like most of people dont have the ghost call issue of gingerbread update. If not they haven't figured it out as it doesn't occur always. I checked it with my home phone. I made 10 calls and 3 of them were ghost calls.
There problem is with the baseband according to my knowledge.
Do we have to wait for the next update to overcome this problem.?

If we did, there'd be a thread about it.
Please use the search function next time.
Sent from my Samsung Galaxy S II w/ DUAL BOOT: CM9 / MIUI

I feel bad for all you people having ghost call issues. I would say for anyone having them to take it to your store you got it and demand a different one. I have tried all the gb kdz's and never once had ghost call issues. It might be a problem specific to individual devices being not everyone has them. And it seems like the people who haven't had GC once, haven't had them ever.
And so I have spoken it.. and so it shall be.

ahh :-( :-(
that means we are not going to receive and GC fixing update in the future. Unfortunatly im outside US and will not be able to go to any store.. :-( :-( :-(

Factory resetting (from the menu and also all options in recovery menu) before and after reinstalling GB did the trick for me. Didn't notice any GCs after that and never got complaints from family anymore. I was on my countries official GB though. When I was trying to use Rogers nothing could have stopped GCs for me.

Im on the at&t baseband. Factory resetting it didn't work for me.

TylDurden said:
Factory resetting (from the menu and also all options in recovery menu) before and after reinstalling GB did the trick for me. Didn't notice any GCs after that and never got complaints from family anymore. I was on my countries official GB though. When I was trying to use Rogers nothing could have stopped GCs for me.
Click to expand...
Click to collapse
resetting dosent make any difference. I did it few times. :-(

speeddevil said:
Im on the at&t baseband. Factory resetting it didn't work for me.
Click to expand...
Click to collapse
Kasvinda said:
resetting dosent make any difference. I did it few times. :-(
Click to expand...
Click to collapse
So did I, for some reason the last time I did it worked. Like I said though, I didn't simply factory reset it. I removed the mem card, formatted internal mem card 3x, factory reset phone from settings 3x, boot phone into recovery mode and performed all wipes 3x, than installed GB on this completely blank slate, than did all that again before using it. I believe I did have 1 GC instance after that, I don't remember for sure if it was before or after I did all that, but than for at least 5 weeks I whenever I noticed white signal bars I dialed a number and sent myself a text. They always worked fine and I never got the RIP message. Also no one ever had trouble getting a hold of me or mentioned that they couldn't, and my wife is very vocal about that. That's how I knew I was having so many problems before the final straw that forced me to try all that. Either way I've now jumped ship and an happily using an iPhone 4S. Sure I miss my custom keyboads and stuff but my phone finally works smooth as silk and I never have to worry about it again.

http://www.lg.com/us/support/message-customer-service
Guys we should report this issue to LG. Otherwise they will not feel our problem...
Please use the above link to report Ghost call issue.

i created a post on facebook support page and you guys should like that so that they will understand this problem is for everyone.
http://www.facebook.com/LGUSAMobile/app_227698805184

Many many problems with KitKat update, what are my options?

I am stock, unrooted, and I installed the KitKat update a couple of weeks ago and my phone is absolutely terrible now.
1. Getting the "no-sim" (no sprint sim, no 4G for you!) error message, which I have never gotten before on this phone. I get the error intermittantly after installing the kitkat update
2. Battery drain is substantial, about twice the rate of what it was before
3. Phone runs much warmer than normal
4. Very bad reception, texts and calls not going through. I used to be able to get full bars 4G in my house, now I don't even get 3G after the update, and I had a 30 minute phone conversation from my house the other day and I dropped the call 4 times.
I thought maybe it was just a tower issue but it's been like this for the past few weeks. I've tried doing a PRL update, profile update, etc. but nothing helps.
Is the reception issue a problem with the most recent PRL update?
If I root the phone and install a custom ROM will this address my problems? I've rooted my tablets before but not a phone. Would going over to CM solve these issues?

I had the same problem way back on this phone and it was the SIM had gone bad. I would definitely expect that yours has just gone bad. That would cause your battery to drain due to constantly seeking network but SIM won't register. Which would also likely cause the excessive heat too.
I hope this is all the problem is for you. It was a simple fix at the Sprint store. Good luck!!!
Sent from my HTC One using Tapatalk

take the sim card out and clean it maybe? and do a factory reset after you backup?(of course, unless you root and use some software to backup, all other backup methods just won't help too much)
Reason been, I had the total stock phone when I did the KK update on Feb 1st I think, and I didn't see any problem other than somehow enabled my google voice. No signal problem(same s..t as the dec update last year, before that it was even worse) and no battery problem(turned on the stock battery saving)

I had problems (2) and (3), and a few others, since installing the update. In my case, the GPS receiving notification would flash incessantly, and Location Services seemed to be the battery drain culprit, I could dramatically reduce the drain by turning the GPS off (not a great solution).
The answer, at least in my case, was a hard reset. I did that, reinstalled my apps, and the GPS / battery issue has gone away. I was also having other intermittent weird issues that have gone away since reinstalling. I guess the upgrade must have corrupted some things...
Sent from my iPad using Tapatalk

Hard reset your phone and clean the SIM card. You should be all good then. Kit Kat should have the opposite effect on your battery life. I usually get 10+ hours on a charge. Matters what I'm doing with my phone.
Sent from my HTCONE using Tapatalk

Just wanted to add that my phone has suffered from none of the issues above. I'm using it on a GSM network in India and running InsertCoin Rom. Everything works well. Battery has been decent and I can easily pull 12 hrs plus
Sent from my HTCONE using Tapatalk

So I did the factory reset this weekend. Just to confirm, the factory reset reverts me back to KitKat, not Jelly Bean, which was what the phone originally came with. Just want to confirm I did the reset correctly.

I dont think you can downgrade from KitKat to Jellybean not on stock atleast.

SeriesOfTubes said:
So I did the factory reset this weekend. Just to confirm, the factory reset reverts me back to KitKat, not Jelly Bean, which was what the phone originally came with. Just want to confirm I did the reset correctly.
Click to expand...
Click to collapse
when you took the OverTheAir upgrade package, it will get into bootloader and change(upgrade) your phone's ROM(not really Read Only Memory any more, but still carry that name) and from then on, you will have to use the bootloader to reload the old jelly bean to get back to JB, otherwise, no matter how you reset, it'll be KK. (the reload process requires special files and procedures, with computer and USB cables) Although "factory reset" won't revert back to the "original factory settings" that came with the phone at the time you bought it, it will wipe out all the settings and apps and anything that's not set by the factory default. After the so called factory reset, your phone will get into a state that the "factory" testers have, which should be a stable state because the "factory" supposed to do a lot of tests based on that state and pass all those tests. This will give you a nice baseline about which could be wrong, the hardware, the network, or the software. Though, it won't be always true because human make mistakes, so the "factory" could release a software that's buggy. like the one we got on last dec, but still, once you get to the so called "factory" state, which all the other phones using the same hardware and software will get to the same point, you can be sure that no other unknown factors are causing your problems. It's like you have the exact same thing on your hand as somebody else on the other side of the planet, so other people can do the tests required to figure out your problems. Will that help you for some apps you want to run that crash your phone or cause big problem? No, that's the responsibility of the apps' developers, not the phone manufacturer. in that case, you'll have to give up that app.