Related
Hey ladies and gents, I have a strange issue with my N5. I am losing data connection despite having a 4-bar LTE signal. Most of the time, I will catch it at work while streaming music from Spotify/Pandora. Once in awhile i'd catch it while browsing Facebook as well. It will show a 4-bar LTE connection, but the apps will report "no data connection available." I've tried surfing Chrome when this problem arises and it says "You are Offline." I found a temporary fix - turning Airplane mode on/off or restarting the phone.
Has anyone ever heard of this, and does anyone have any suggestions. I was running SlimKat before, but now i'm on stock 4.4.4 with ElementalX kernel, with the issue crossing multiple ROMs/wipes.
I also just got off of chat with Google support. The lady is emailing me some troubleshooting steps, and wants me to contact T-Mobile as well. If the problem is still there, she wants me to RMA. What are the steps needed in order to do so. Some quick searches brought up factory images but I haven't found anything recent, and want to make sure I have all my bases covered.
Thanks guys!
Google doesn't care whether the bootloader is unlocked or whether the phone is rooted. If it's a hardware issue, you are covered!
If you want to return to stock before sending it in for peace of mind then follow this thread: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Sorry for the late reply, been pretty busy the last couple of days. Glad to hear that Google doesn't care about the unlocked bootloader! I'll probably just return completely to stock and return it like that IF I have to.
However, I think I may have fixed the problem. I altered my APN settings and changed IPv6 to IPv4 and it seems to have fixed my problem, at least for now (the problem is random so i'll have to use it for awhile to make sure it really is fixed). Anyone else ever heard of this problem, or this fix, especially on T-Mobile?
Hi, i was happy seeing that the dev of the CM/Carbon/Slim-Roms didn't just stop but moved from the old original shabbypenguin-thread to xda
the latest Carbon-Build ( CARBON-KK-NIGHTLY-20140825-0209-peregrine.zip ) finally works for the most part on my side, pretty happy with that.
unfortunately 2 things aren't and i wanted to see if anyone else has this issues or has some idea to solve them
first one is, that WiFi won't connect to all networks - at home on a netgear-repeater everything is fine - in the office it won't connect to D-Link and TP-Link routers.
the other, more troubling issue is that bluetooth isn't working as it should - as long as no device is connected, everything is fine, but as soon as it connects to my car-system (MB C-Class w204 without command if that makes any difference ) the bluetooth-process stops, reconnects, stops again and so on...with my laptop everything seems to be working fine and i think the first drive after coupling also worked fine - any idea what can be the cause of this? never had this kind of problem before, be it stock or older unofficial CM-Builds etc...
i'm refering to this thread btw: http://forum.xda-developers.com/moto-g/4g-development/rom-carbonrom-kitkat-t2847887
regards
Termuellinator said:
Hi, i was happy seeing that the dev of the CM/Carbon/Slim-Roms didn't just stop but moved from the old original shabbypenguin-thread to xda
the latest Carbon-Build ( CARBON-KK-NIGHTLY-20140825-0209-peregrine.zip ) finally works for the most part on my side, pretty happy with that.
unfortunately 2 things aren't and i wanted to see if anyone else has this issues or has some idea to solve them
first one is, that WiFi won't connect to all networks - at home on a netgear-repeater everything is fine - in the office it won't connect to D-Link and TP-Link routers.
the other, more troubling issue is that bluetooth isn't working as it should - as long as no device is connected, everything is fine, but as soon as it connects to my car-system (MB C-Class w204 without command if that makes any difference ) the bluetooth-process stops, reconnects, stops again and so on...with my laptop everything seems to be working fine and i think the first drive after coupling also worked fine - any idea what can be the cause of this? never had this kind of problem before, be it stock or older unofficial CM-Builds etc...
i'm refering to this thread btw: http://forum.xda-developers.com/moto-g/4g-development/rom-carbonrom-kitkat-t2847887
regards
Click to expand...
Click to collapse
*push* nobody got any ideas? i would post it in the appropriate thread (especially since this rom is still only nightly) as a potential bug report, but as a new user i'm not able to :/
just another push...somebody must have any idea on what i can try to either solve or at least track down the cause of the issue(s)
sure enough, the BT-issue is worse..
tried the newest build (dirty update and after that clean flash), but still no luck
Termuellinator said:
just another push...somebody must have any idea on what i can try to either solve or at least track down the cause of the issue(s)
sure enough, the BT-issue is worse..
tried the newest build (dirty update and after that clean flash), but still no luck
Click to expand...
Click to collapse
The WiFi bug is a known issue since early August. It affects almost every Moto device (G, G 4G, X and defy?) it's reported several times to CM-s bug tracking system, but nobody cares... You can use custom kernels. Maybe they aren't affected.
I don't know anything about the BT bug.
i found some posts about people having the same kind of wifi-issue, but it is good to know, that the devs are aware and - kind of - working on it
the BT-thingy is driving me insane though...fiddled around a bit, stopping BT-Related processes etc...this somehow did something...my phone now connects and stays connected, i can make phone calls...but the contact list is incomplete - only 3 random contacts are displayed on the car system
haven't rebooted since then, i kind of fear that rebooting will bring back the issue :/
BT still working after reboot, so it seems my "fix" is permanent...must have something to do with deleting the BT-data/cache while process was killed i would think - in case someone else also encounters this problem
still can't acces all my contacts from Car-system though :/
Most nights roms have a lot of issues and it is pretty hard to stay aware all of bugs. Why don't you try something more stable like Pac Man RC or some. Sometimes a different kernel will help sometimes it's the opposite.
Well, i'd rather use a stable version for sure...
sadly, i didn't know about falcon<->peregrine, so i thought i can use all the Moto G roms with my xt1039...
and to this date there are no stable roms for peregrine that i am aware of - an old unofficial CM-Build worked pretty good for me, but CM unfortunatley doesn't offer all the features i want - carbon covers pretty much most of it, so i'm hoping that it will be "bugfree" soon enough ^^
Termuellinator said:
Well, i'd rather use a stable version for sure...
sadly, i didn't know about falcon<->peregrine, so i thought i can use all the Moto G roms with my xt1039...
and to this date there are no stable roms for peregrine that i am aware of - an old unofficial CM-Build worked pretty good for me, but CM unfortunatley doesn't offer all the features i want - carbon covers pretty much most of it, so i'm hoping that it will be "bugfree" soon enough ^^
Click to expand...
Click to collapse
All AOSP rom uses the CM device tree and kernel as a base, so the low level kernel bugs are the same.. Also the last "stable" CM for falcon is dated back to April, so you didn't lose anything with peregrine...
Just in case anyone encounters the same Issues:
with CARBON-KK-NIGHTLY-20140922-0414-peregrine the BT-Problems seem to be resolved, connection works and the contacts are accessible from the car.
WiFi still has problems with dhcp, but as stated, devs are aware of that :good:
bad news: flashed to CARBON-KK-NIGHTLY-20141103-0939-peregrine and the BT-issue is back as in the beginning - com.andoird.bluetooth stops working - but only following the first connect -.-
interestingly going back to my pre-flash-backup didn't resolve the issue (doesn't matter if i just restore or wipe prior to that...but after flashing/restoring the first connect works perfectly)...perhaps that leads to some ideas about the cause?
was just trying to get it to work like the other time by stopping/deleting data of com.andoird.bluetooth, but didn't work this time
ok, figured it out again, this time i'll post my steps in case anyone ever encounters similar issues (and for my future reference in case i encounter them again, too )
1) unpair
2)switch off bluetooth
3) stop com.android.bluetooth in "apps"
4) delete data of com.android.bluetooth
5) reboot
6) pair
7) unpair
8) delete data of com.android.bluetooth
9) pair
10) reboot
at least these are the steps i did and it seems to be working now, again
Please help with the "hello hello bug" (2-3 secs delay when answering a call)
There are lots of old threads about this, but I can't believe this is still an issue. You know the same old problem - When I answer a call the first 2-3 seconds the other side does not hear me, then everything is fine. It is called the "hello hello" bug or "Call Delay" bug, The oldest posts I see that explain the same issue are from 2011. Now 3 years later this is still NOT fixed. Come on Google get your **** together seriously...
It seems that every android phone that I've owned had this problem. This is my 2nd nexus 5 (the first had memory problems) and I still experience the same bug.
Anyway is there a known fix for this? Does anyone had this problem and fixed it somehow? I've read that there was some "Call Delay Patch" but I cannot find a working link for this, the app is no longer in the play store also.
I am experiencing the same issue since I bought the phone, even changing the rom to CM11 did not change the situation. Does anyone have an answer to this problem?
no issues here, im using lichtis rastakat build with trinity kernel.
bump bump.. Is no one else experiencing this issue? Saying hello 2 times after answering is a bit annoying .
I've experienced this issue as well, but I've only noticed it when I'm communicating with an iphone user. It never happens when i call or receive a call from someone on landlines or android phones.
I my case this happens with litteraly any type of phone. This is a really weird bug because it doesn't seem to be device specific, i had this happen to me on my old lg optimus black, but then installing a different rom, fixed the bug, now this happens on all the roms i've installed.
Could it be baseband specific?
This happens on every Lollipop ROM I have flashed, no problems on 4.4 ROMS. I do clean installs, do not restore anything from Tibackup. So basically what happens is I will randomly but very frequently lose all data and cell service. Like once every three minutes frequently. It only lasts about 5 seconds at a time. The signal bar triangle will have an exclamation mark in it (see attached example). I delete and re-enter my APN, turn off wifi AND the Scanning Always Available option. I have read some threads about this exact same thing happening on Nexus 5 after Lollipop update but they are old and it seems to have been fixed with an update. Does anyone have any ideas about what is going on? I'm on TMO in the US and like I said, it ONLY happens on Lollipop ROMs it does not happen of Kitkat.
I read this as sort of an explanation as to why but nothing as to how to fix it. It is driving me insane.
I'm in the same boat, I cant make calls with hangouts or with Dialer or it will disconnect. I haven't seen a solution yet. I've tried every ROM I can, but it keeps crashing. drives me up a wall. I want to logcat it, but having issues while at work.
budm said:
I'm in the same boat, I cant make calls with hangouts or with Dialer or it will disconnect. I haven't seen a solution yet. I've tried every ROM I can, but it keeps crashing. drives me up a wall. I want to logcat it, but having issues while at work.
Click to expand...
Click to collapse
Only discussion about this I have seen is in the Nexus 5 forums, nothing in OPO
Any insight to this would be greatly appreciated.
Come on guys, am I really the only one with this issue?
TigerDNA said:
Come on guys, am I really the only one with this issue?
Click to expand...
Click to collapse
You're not alone, I have this as well but I don't get the exclamation mark but instead the triangle appears completely empty, as if I have no signal at all.
anyone know a way to fix this awell? i flashed the new lolipop alpha modem and still same thing if not worse
The only time this has happened to me is when I toggle Wi-Fi. It for this every time, but have no data issues otherwise. Seems to be when switching between ip addresses. Are you possibly between towers or roaming on another network? May be the issue, but I can't say for sure. Running the lollipop rom exodus, no issues at all.
EDIT: also what baseband are you guys on? I thought I saw something similar and someone flashed a test baseband and it fixed whatever issue they were having. Link coming shortly.
EDIT 2: just now noticed the list above mine about the alpha modem and it not working for them. If anyone else needs to try however, link is http://forum.xda-developers.com/sho... work for some and not others.
from the one+
Does anyone know if we can flash the CM11S modem on CM12?
Go to Settings -> More - > Mobile Networks. Make sure all the items are set correctly.
alleykat2561 said:
Go to Settings -> More - > Mobile Networks. Make sure all the items are set correctly.
Click to expand...
Click to collapse
In OP "I delete and re-enter my APN, turn off wifi AND the Scanning Always Available option."
Same issue here. Running SlimSaber using alpha radio.
Same problem on two OPOs here, both running Temasek CM12
Anyone found a solution yet?
I have the same issue on CM12, BlissPop and Validus ROMS.
Strangely I do NOT have the issue on Euphoria.
Think it happened after I flashed the Alpha L modem.
Tried flashing an older CM11S modem, but no luck...
Hi,
Sorry for the noob answer but anybody tried settings>mobile networks>preferred network type and set it to 3G? I flashed a new rom from stock CM and noticed that I was experiencing signal trouble, I checked my status and the signal detected is LTE so I changed my network to 3G and network signal improved. Downside is that you cant use LTE (but thats ok for me since here in our country, LTE signal is still kind of limited)
Zino same for me. Ever find a fix or a rom that doesn't do this?
OP here, it's strange that all of us have this issue, the same issue that came up on the Nexus 5 thread when L was first released but know one else seems to have any knowledge of it. I am almost certain it doesn't have to do with our carriers but rather something software related.
I'm also suffering from this issue, until now the only way I knew how to fix it was to wipe the cache in recovery which takes ages!
got the same problem :<
I have a similar issue. I use t mobile in the USA and LTE works, H+ works, but 3g shows signal and won't load anything. No idea how to fix it.
Hey guys, I was wondering if anyone else has this problem. When using the official COS 13 rom everything works but GPS is slow to get a fix and when it does, it is out of sync i.e. position is further back or forward from my real location.
When I flash to Nougat, GPS works as it should, locks pretty quickly and is accurate. I've tried changing modem firmwares, using TopNTP to patch the gps.conf file and nothing seems to work in COS 13, which is the OS I prefer since Kali Nethunter works on it with no hitches.
I would really like to go back to COS13 but I use GPS occasionally and as the old saying goes, you only wish you had it when you need it the most. Any help or thoughts would be appreciated. Thanks.
Guess no one else ever heard about this.
It's not that nobody has heard of it, but you're asking about an issue with an older version of Android that is no longer being actively developed, and due to security flaws is no longer safe to run on your handset. As with all versions of Android, the code is open sourced, so you are more than welcome to dig into the source code, get your hands dirty, and fix anything you want, but expecting anyone else to fix an issue on a deprecated OS is a bit much, IMHO.
Never asked if anyone can fix it, I won't be so bold since I never did any Android development myself, hence is stated I flashed different firmware and used GPS.conf apps etc just asked if anyone else came across this issue since at one point in time we were all on cos13 and if it could be solved by flashing a zip or editing a conf file.