Related
I'm not sure if this is the same as the well known "Nexus One 3G problem". I'm running CyanogenMod 6. I have been having occasional trouble on my home carrier (WIND Mobile Canada) where every once in a while, even though the 3G or H icon appears, I can't access anything and when I try the ping test under Testing/Phone information it fails.
The only way I'm able to get the Internet back is to disable mobile data (via widget) and re-enable. Then it lasts again for a while.
I'm currently on vacation in the US and using a T-Mobile SIM. It seems this problem is even worse on their network. Sometimes I only get maybe 2-5 minutes of a 3G connection before it freezes out like this. I've been leaving it on EDGE just to keep it stable, but this is obviously not an ideal solution.
About two weeks ago I started trying nightly builds of CM6 as I was interested in the FM Radio, and I have noticed this issue much more since then. It might be related, but it could also be a coincidence, and I don't want to start messing around with multiple ROM flashes while on vacation if that's not the problem in the first place. Any ideas on what to do?
Thanks
Charles
its a bug with 2.2.1,my nexus does this too. it will get stuck with the data up arrow lit up when the data stops working,turning data off and back on fixes it. there is even a post in the google bug tracker about it. I know for sure it happens in both FRG83 and FRF91,but I'm not sure exactly when it started. 2.1 roms for the N1 don't do it,and my g1 doesnt on 1.0-2.1,but on froyo roms it does exactly the same thing as the nexus.
I hope someone (google or a dev) can fix this,because its really annoying. my g1 is back to donut because its faster,and I'm considering going back to a 2.1 rom on the N1. I've confirmed the issue on ChromaticDream (g1),CM Nightlies (I've tried 198,200,201,202,203,220),CM6.0.0,Enomther's TheOfficialNexus (10/11/10),and a few others.
I thought I was the only one who noticed this bug. Does it occur in the stock (non-rooted) versions of 2.2.1 as well?
Just an update, although I do periodically experience this on my home provider (WIND Mobile Canada), it turns out that T-Mobile is having 3G issues in Portland this exact week and everyone's experiencing it. So the fact that 3G is nearly unusable on my trip is TMo's fault and not Android's.
UPDATE: I downgraded my radio to the official froyo radio (4.0-something lol) and my timeout problems are no more so far....
I have the same problem but with since I'm using nightlies 215 the problem is gone (i'm using 508 radio)
but lately I'm using nightlies 221 and 223 and the problem is back
I settled on 204 for vacation because I didn't want to fiddle with the ROM 10 hours away from my desktop comp! Now that I'm home, keep this thread updated with which builds seem to have a stable 3G connection.
I just flashed 225 with 512 radio and I can say this build is stable, no more intermittent connection lost. 225 nightlies is fast as well
Good to know. I'm on the 5.08 radio; is there a significant difference with 5.12?
Hey
For the past month or so I have been playing around with a few builds of ICS for captivate. I started to notice that whichever build I used whether it was teamhacksung or miui I didn't have 3g. I changed my APN multiple times, tried different radios and it go to the point when my signal in my basement (where I get crap for signal) showed full bars and 3g except the speed was terrible. Is this a common issue? Anyone able to give me a hand?
I just recently went back to my old backup of CM7 and my 3g works flawless.
Veight said:
Hey
For the past month or so I have been playing around with a few builds of ICS for captivate. I started to notice that whichever build I used whether it was teamhacksung or miui I didn't have 3g. I changed my APN multiple times, tried different radios and it go to the point when my signal in my basement (where I get crap for signal) showed full bars and 3g except the speed was terrible. Is this a common issue? Anyone able to give me a hand?
I just recently went back to my old backup of CM7 and my 3g works flawless.
Click to expand...
Click to collapse
Since it's not fully developed yet, there can be random bugs like that. Try a factory reset and a full reinstall. If that doesn't work, you may have to try going from stock
Sent from my (CM9) ICS i897 Captivate
Thanks. I'll give it a shot.
Add: by starting from stock you mean what exactly?
Sent from my SGH-I897 using XDA App
Veight said:
Thanks. I'll give it a shot.
Add: by starting from stock you mean what exactly?
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
Stock as in flashing back to froyo or eclair, and then however you want to get to ICS
i'm having some what the same problem but with H20 setting not working right. i get talk and text but no internet or mms, and even the setting disappear after i save then
Since upgrading will take you off the upgrade path, I was just wondering if there is something on the new build that isn't working.
Like camera, video, data etc.
Honestly, I wouldn't jump on it unless you really need it (I've heard it makes GSM work a lot better). AFAIK, it hasn't even been rooted yet, which means you are giving up a LOT just to get ICS, which you can do from the stock rom and safestrap.
If you root just before flashing and use voodoo rootkeeper you can keep root. I unfortunately forgot to re-root after I needed to flash SBF (wouldn't update). So far everything works for me. Well except root that is. But to tell you the truth. I only used root to change the build.prop and have write access to system (notifications etc). Owh and freeze apps. But thats it.
So far so good! The battery won't last as long as on 219. But by how much I'll have to test. On 219 I ran in 2G mode all the time. So it isn't a real fair comparison. Yesterday I turned off all sync and push and disabled some applications. So we'll see how long it will last today.. I took it off the charger around 07:50 AM. So don't expect an update 'till tomorrow. It's only 08:50 AM where I live .
For the gsm users i recommend this update if you can go with no root
The rom is actually more responsive and most importantly, it dun drop the line that often
And ics with WORKING camera & video, not much is missing actually
According to this, you can keep root if you install OTA Rootkeeper, back up root, temp unroot, restore root, and THEN apply the update.
I updated and kept root and am very impressed with every aspect of performance on this build.
Battery life the first day was excellent, above average considering I was playing with the phone a lot.
Radio performance on VZW's network with this new baseband is exceptional.
Data throughput and transitions from cellular to WiFi and maintaining data connection were all distinctly improved. I am in a marginal 3g only area where I live and work 90% of the time, but I can go a few miles away to get LTE coverage.
While I cannot openly recommend flashing non revertable leaks to anyone, I cannot say enough about how much I am enjoying this build right now. I have yet to find any downside beyond the fact that we have no full firmware files for this build yet.
This is a superlative build and anyone willing to accept the risk should not be disappointed.
25 hours later there's 30% battery remaining. Made 5 1-minute phone calls. Played about 20 minutes of 3D games. Used internet a couple of times (checked email, whatsapp, some internet apps) and I would say at 90% 3G connection. So that's not so bad I would say.
Stuff not Working
For me, my Facebook app (built-in) is not working, and constantly crashes. I finally disabled the app completely to stop getting the crash pop-ups.
Also, built-in MotoCast disappeared, and it does not show up for me in the Play Store (probably because they have not released an ICS version of the app for non-tablets yet in the Store).
Other than those 2 so far, everything I have tested and checked works like a dream come true.
Everything is working great for me. The ota rootkeeper worked as well. Im running the leak with root.. the facebook app that came on the leak needs update. Its an older version. May be the reason
Sent from my DROID4 using xda premium
Anyone else have problems with the headphone jack not working?
Everything seems to work fine for me so far.
Motocast is built in to "My Files", "My Gallery", and "My Music" now. I just installed it and seems to work fine.
Negative. Just drove 20 hours with headphones on.
Sent from my DROID4 using xda premium
What's the battery like for GSM users on 3G with the new leak?
Sent from my XT860 running ICS
I also am having problems with the headphone jack. Is there a fix for this?
mcochon said:
I also am having problems with the headphone jack. Is there a fix for this?
Click to expand...
Click to collapse
Please be more specific about the headphones.
I haven't had any issues with Klipsch X10 headphones at all, but mine is only a 2 prong headset, without microphone or call control features.
I've had some odd headphone issues and I am NOT on the leak.
I'll plug in headphones, but the phone won't switch from the loudspeaker to the headphones. Unplugging and replugging the headphones in usually fixes the issue. Kind of annoying, but I use headphones so infrequently on my phone anyway that I haven't done any hard investigating on whether it is a software or hardware issue.
I'm leaning towards hardware though, because IIRC it happens on stock and the GB-ICS frankenbuilds.
This may be a stupid question but does anyone know if there is going to be a way to reverse being taken off the upgrade path? Im new to the forums and I just started getting into rooting and flashing roms. Im running a nightly build of the aokp ics with cm9. Im happy with it so far but would love to use my camcorder again lol. Are there any other issues with this version of ics?
I dont know about reversing the upgrade path but i do know that everything works really great on my d4 running the leaked ics.
Sent from my DROID4 using xda premium
anon117 said:
This may be a stupid question but does anyone know if there is going to be a way to reverse being taken off the upgrade path? Im new to the forums and I just started getting into rooting and flashing roms. Im running a nightly build of the aokp ics with cm9. Im happy with it so far but would love to use my camcorder again lol. Are there any other issues with this version of ics?
Click to expand...
Click to collapse
You SHOULD be able to get back on the upgrade path using the same method others have used to go from the .200 ICS leak to the .206 ICS leak. That involves a partial flash of the .219 fastboot file to essentially trick the update into thinking you are still on .219. But there are no guarantees.
I see. Thank you for your input. One more thing does anyone know if the gummy rom has been updated? I was using it for a few days but decided to go to the aokp for better 4g functionality.
My girlfriends D3 has gradually been getting worse with poor reception, dropping calls, not being able to make/receive calls or texts.
Data seems to work fine. This weekend it just finally stopped being able to make calls or send texts from our home.
If i drive a few miles down the road or to a higher elevation i was barely able to call *228 to update roaming.
I can still use the browser over 3G and Wifi, just no tethering, phone or text.
The phone shows 3G and a full signal, but as soon as i initiate a call it drops to 1 bar.
Another thing we noticed this morning is that when calling the phone it goes straight to voicemail.
I had tried changing the Network mode from Global to CDMA yesterday and at one point got an error message saying "No CDMA networks were found. Would you like to switch to Global Mode?"
Phone has been rebooted and battery pulled along with some other diagnostic tests that the verizon techs did over the phone yesterday.
The only thing i had done to this phone was i applied the TBH tethering hack without root over a year ago. It worked fine up until now.
The phone has the latest System version 5.7.906.XT862 and the latest Baseband N_03.18.32P.
Im thinking of reverting the TBH Tethering hack back using the instructions in this post
I spoke to Verizon tech support yesterday and they said there was some trouble in our area, but my Droid X is still able to connect so i doubt thats the issue.
Does anyone think that an OTA update from Verizon may have screwed something up due to the TBH hack being applied?
The GF is frantic about getting her phone back. I can take out insurance for 6.99 pr/month and pay $100 to get her a new phone, but if reverting the TBH hack and maybe rooting and installing a new ROM might help, im all for it.
Any thoughts? ROM advice? Was reading up about the AOKP Build 40 ROM, but wondering if all the hoop jumping will help or if the D3 has a hardware issue that has just got progressively worse.
Wont you help a poor guy keep the peace with his lady please?
I don't think it's that. It's possible that the 3G in the area is good but 1x is crap. 3G is just used for data while calls/texts are used on 1x. What is the PRL versions your phone and her phone have?
MrObvious said:
I don't think it's that. It's possible that the 3G in the area is good but 1x is crap. 3G is just used for data while calls/texts are used on 1x. What is the PRL versions your phone and her phone have?
Click to expand...
Click to collapse
My Droid X running on VXLR V2.2.0: PRL 53018
Her Droid 3 Stock w/TBH Tethering Hack: PRL 52996
Just tried updating them both and the PRL's stayed the same.
About an hour ago i was in the middle of backing up her phone and it started ringing. I was able to answer the call and now im able to make and receive texts and calls. There must have been a tower issue. The signal still drops to 2 bars when i initiate a call, but at least its working again.
She says its been flaky for quite a while with dropping calls and texts not getting sent. Im all backed up and was thinking of rooting and trying a ROM on this. Not sure if itll help with signal issues, dropped calls or texts not being sent or received.
She was also complaining about the thing pocket dialing, and other random stuff happening like her browser launching and texts being sent etc. I saw it this morning. I picked up her phone to bring it downstairs and saw that there was a text reply box open with a bunch of jibberish typed in it. She says that sort of thing happens all the time.
Think maybe a good stable ROM might help?
After a little more research i came across Minimoto here at XDA. Minimoto Link
Seems to be the way to go if im sticking to a GB ROM. I see you contributed some to it. Would you happen to know where some step by step instructions for getting it installed on a non rooted D3 might be?
1) Root it.
2) Install Safestrap 3.05.
3) Reboot to it, create ROM-Slot 1.
4) Factory reset and wipe cache and delvik.
5) Flash the ROM.
6) Set her up with goodness.
Though if random crap is popping up, I suspect the digitizer is flaky.
MrObvious said:
1) Root it.
2) Install Safestrap 3.05.
3) Reboot to it, create ROM-Slot 1.
4) Factory reset and wipe cache and delvik.
5) Flash the ROM.
6) Set her up with goodness.
Though if random crap is popping up, I suspect the digitizer is flaky.
Click to expand...
Click to collapse
Have you heard of digitizer issues with D3's before?
Any recommendations on which rooting method to use?
Do i have to remove the TBH Tether hack before rooting, installing Safestrap or Flashing the ROM?
So i take it your in agreement that this would be a good choice for a stable no frills GB ROM?
the random stuff can be from from a bad digitizer, dirt/grime on digitizer/edge or a software conflict
try cleaning screen around the edge, and/or flash rom/sbf
you need to remove bootstrap before safestrap, tbh hack should be fine
i haven't use minmo, but many have, also you could look at
http://forum.xda-developers.com/showthread.php?t=2106722
use the Deodexed ROM (Courtesy of thingonaspring) link
sd_shadow said:
the random stuff can be from from a bad digitizer, dirt/grime on digitizer/edge or a software conflict
try cleaning screen around the edge, and/or flash rom/sbf
you need to remove bootstrap before safestrap, tbh hack should be fine
i haven't use minmo, but many have, also you could look at
http://forum.xda-developers.com/showthread.php?t=2106722
use the Deodexed ROM (Courtesy of thingonaspring) link
Click to expand...
Click to collapse
Thanks sd_shadow I think ill stick with minimo most likely. Too many dam ROMS to choose from!.
Ok so from the hours of reading i did yesterday, i found a working link for motofail. It appears it is the best (or only) way to root the D3 if on 906.
From there i thought i could just install Safestrap 3.05 which i managed to track down as well.
I never installed Bootstrap, so does this even apply? Is there a factory bootstrap included with the D3?
I believe i read that minimoto has its own tethering feature included. So are we sure i dont have to revert the TBH tethering hack?
Some great links in your signature by the way. If the digitizer keeps acting up, i may try replacing it. I did clean it last night and will see if things improve.
LOTL said:
Thanks sd_shadow I think ill stick with minimo most likely. Too many dam ROMS to choose from!.
I think your the only person to say that for the d3 lol. Most of us are flash- a-holics and we love lots of roms to chose from.
Ok so from the hours of reading i did yesterday, i found a working link for motofail. It appears it is the best (or only) way to root the D3 if on 906.
From there i thought i could just install Safestrap 3.05 which i managed to track down as well.
I never installed Bootstrap, so does this even apply?
Just install safestrap on your safe system after root don't worry about bootstrap.
Is there a factory bootstrap included with the D3?
No
I believe i read that minimoto has its own tethering feature included. So are we sure i dont have to revert the TBH tethering hack?
No you do not have to undo the tether hack it is a hardwear hack not a software hack and will work on any rom no matter if the rom already has tethering in it.
Some great links in your signature by the way. If the digitizer keeps acting up, i may try replacing it. I did clean it last night and will see if things improve.
Click to expand...
Click to collapse
Sent from my DROID3 using XDA
replacing the digitizer is a pain
some [how to] links in my list
So I have the T-Mobile variant of the LG G4. I had it unlocked straight from the carrier a while ago and all seemed well. Recently I noticed a huge amount of battery drain and 4G LTE usage from T-Mobile's pre-installed apps--mainly com.tmobile.pr or something which is the "My Account" app (imagine being at 60% left with 27% of the drain having been an app and only 9% the screen. Yeah, it was that bad)
This I obviously found unacceptable, so I went ahead to try and uninstall the bloatware. Lo, much to my dismay, Tmobile has locked it down so you can't uninstall the bloatware, and you can only disable it. This alone irked me enough that I wasn't satisfied with just a disabling. I knew I wouldn't rest until I had obliterated it.
I've had plenty of android phones over the years and done my fair share of rooting and flashing ROMs and the like, but I hadn't touched that aspect of my G4 because I wanted a dependable device for school and I didn't want to mess around with it. I knew I'd have to root it to get rid of the tmobile bloatware so I went and did that using the Low effort root method (http://forum.xda-developers.com/g4/orig-development/root-tmo-vzw-intl-variants-soon-root-lg-t3164765). When this was done a lot of my background processes started to continuously crash. I decided to go ahead and put TWRP as the custom recovery and just go ahead and get some dependable 6.0 ROM, and I found a couple of them.
When I flashed the first ROM, the play store services were crashing so I found the google apps package for marshmallow and flashed that too. It seemed to fix the issue. Yet when I would click on my School's WiFi at the setup (which is WPA2 Enterprise) it would crash and say "Unfortunately WiFi has stopped working." I thought that perhaps I mucked something up in the flashing of the ROM, or that maybe there was an issue with the ROM in general, so I decided to just flash another ROM entirely (after factory resetting it all the way). Along the same time as this I found a slightly more modified and feature packed version of marshmallow by this lad here (http://forum.xda-developers.com/g4/development/h815-genisys-rom-1-0-classic-v10g-t3192649). I decided to go ahead and use this one since it had a h811 version there, that involved flashing a h815 and then flashing a patch.
The "Unfortunately WiFi stopped working" issue persisted, however. I found this odd. I then noticed that if I click any other network that ISN'T the WPA2 enterprise network my school is working that everything seems to work fine.
I went ahead and factory reset it all the way again in the hopes that would fix it. No luck.
I booted it to safe mode and tried to connect to the WiFi network from there. No luck.
I downloaded a third party WiFi app off cellular and tried to connect from there. No luck.
I can't enter the WiFi's name and try to enter directly because it crashes there too.
I can't "Forget" the network as it's never joined that network before so there's nothing to forget. It does let me enter the advanced options but a direct press causes it to crash.
So throughout ROMs and wipes and safe modes and all, this one issue has persisted, where my phone's WiFi will crash when it tries to connect to my school's WPA2 Enterprise network. I've tried plentiful fixes short of flashing back to a 5.0/5.11 stock (which I'm hesitant to do because I read something about phones bricking after they downgrade from Marshmallow using the .kdz files or something?).
I'd really appreciate any help that y'all can provide. I've read these forums for ages but this will be my first time making an account because I can't find anybody else with the same issue and its proving to be quite a pain.
tl;dr wifi isn't working with only one particular network and no fix I've tried under this sun has worked so far. help will be appreciated pls
Have you tried flashing this rom here --> http://forum.xda-developers.com/tmobile-g4/development/rom-g4-h811-xtreme-rom-v1-0-7-28-15-t3167667
I am using this one here and I have no issues using wifi. I cannot speak for the 6.0 roms because LG has not dropped the sources for the Tmo variant yet.
esjames said:
Have you tried flashing this rom here --> http://forum.xda-developers.com/tmobile-g4/development/rom-g4-h811-xtreme-rom-v1-0-7-28-15-t3167667
I am using this one here and I have no issues using wifi. I cannot speak for the 6.0 roms because LG has not dropped the sources for the Tmo variant yet.
Click to expand...
Click to collapse
I got the brown leather variant from Tmobile and it only says H811 as far as I can tell. Not sure of if its the "n" version or not.
I have not tried that rom but ill be sure to give it a go, hoping it will help solve the issue. I did some additional testing and can confirm the issue lies with all WiFi networks that employ WPA2 Enterprise security.
Will there be any issue with the Rom when downgrading from Android 6.0? I was reading about phone's bricking when trying to downgrade certain versions or bootloaders on the tmobile variants.
I'm pretty sure going back to stock 5.1 will be fine. The Tmo variant hasnt been upgraded to 6.0 yet and the ports don't update the bootstacks. Read here --> http://forum.xda-developers.com/tmobile-g4/development/global-marshmallow-6-0-port-to-h811-t3232760
Update: It seems that any Android 6.0 flash cuts off the ability to connect to Enterprise wireless networks. I went ahead and flashed to the debloated stock rom on the thread you mentioned, but it cut off the ability to record video. As such, I went for the xTreme version that you mentioned, and flashed the camera restores and all.
Everything works fine now as far as I can tell. I also got rid of the Tmobile applications draining the battery and all that. All should be well. Thanks again for the help