Im seeing multiple people saying that they have WiFi calling on Project Fi running a latest AOSP ROM like Chroma or AOSiP, but I cannot get it working. You cannot put phone into airplane mode to force test it, so how are you verifying it is going over WiFi? It is supposed to show the SSID in the call, but I cannot get it to do this, even with poor to no cell service.
EDIT:
It is not working. Either people were lying or dont understand how wifi calling works for Fi, but once asked to perform a screen shot, they changed their answers to, it doesnt work, but everything else does. Which all AOSP ROMs have before.
droidkevlar said:
Im seeing multiple people saying that they have WiFi calling on Project Fi running a latest AOSP ROM like Chroma or AOSiP, but I cannot get it working. You cannot put phone into airplane mode to force test it, so how are you verifying it is going over WiFi? It is supposed to show the SSID in the call, but I cannot get it to do this, even with poor to no cell service.
Click to expand...
Click to collapse
These ROM's don't let you put it Airplane mode so the toggle isn't there or doesn't work?
Will update 1st post.
It is not working. Either people were lying or dont understand how wifi calling works for Fi, but once asked to perform a screen shot, they changed their answers to, it doesnt work, but everything else does. Which all AOSP ROMs have before.
The latest Pure Nexus ROM worked for me. I noticed there was a third file posted along with it called a "Google dialer.". Required to work with project Fi. I did a clean install (wiped everything) since I had wiped my phone clean anyway, and installed the stock ROM (after being used to Chroma).
Turning on airplane mode on my phone, then Re-enabled my WiFi connection. Made a call as usual, and it went through. On both the stock rom and Pure Nexus.
How can I know for certain that I am getting WiFi calling, other than knowing I had disabled my cellular radio? I would be more than happy to install software and take a screenshot to help. I'd been using Chroma as my goto ROM on my nexus 5, so I did the same after the small nuisances in Stock 5.1.1, like pocket dialing. I really would prefer an led notification over a whole screen one. But that's just me. I hope I helped some.
Related
I have been having intermittent signal problems on my phone for several months now and it's extremely frustrating. I've read through quite a few threads trying to find a similar problem, but nothing seems to provide a solution. So here goes my feeble attempt to explain what's going on...
For starters, I am in Canada on the Telus network. The phone works fine when I am traveling between places but doesn't work at all whenever I am at work or at home. Other places seem to knock it out as well. It hasn't worked at work since I started having the connection problems back in February or March. The same goes for at home. Anytime I am in between the two, which is a five minute drive I can switch the airplane mode on and off and it will usually connect to the network. When the Network drops, I still have signal bars, but get the "emergency calls only" instead.
I am running CM 7.0.3, and have updated the radio to 5.08.00.04 as well as 5.12.00.08 both did not to anything(I am now back on .08). I was on CM 6.1 when the problems started, and have been updating through the release candidates up to the latest stable CM still with no luck on figuring out what is causing the problem. I have done full wipes, as well as installed different ROMs trying to find what's causing this.
Could the SIM card be the culprit? Even if it seems to work fine some of the time?
I'm completely out of ideas, and sick of not being able to use my phone, as an actual phone, while I'm at home or at work. Any suggestions or ideas/questions is appreciated to figuring out what is going on, I'll answer the questions as best I can.
Thanks,
Chad
I'm having the exact same problem as you: only "Emergency Calls" at places with thick walls (is that well said?), where I used to have good reception and where others (with same company) have a pretty decent signal. I really don't recall when this started, but also does occur with all radios and kernels I've tested so far.
I'm currently running CM 7.0.3 with radio 5.12.00.08 and kernel redstar 2.6.38.7-CFS.
Me three. I think its something to do with cyan 7 because its been since I went onto it that signals not been what it used to. Perma emergency only in my halls.
Wifi turns off automatically and it's impossible to make it work again without rebooting. Am I the only one with this issue?
https://code.google.com/p/android/issues/detail?id=80028
quarara said:
Wifi turns off automatically and it's impossible to make it work again without rebooting. Am I the only one with this issue?
https://code.google.com/p/android/issues/detail?id=80028
Click to expand...
Click to collapse
I have a variant of this, I've tried with both the .03 and .04 radios, it's the same, so it's not the radio itself:
I lose coverage so I get the wifi icon with the exclamation mark, instead of it reconnecting automatically. Switching wifi off, then back on, allows me to use wifi again.
I'm using the NX5 AOSP ROM, 5.0R6 (LRX21T)
We all get different experiences, but it sounds like the root cause is likely the same.
Give as much information as you can (Android version, radio, which particular ROM, usage), otherwise it's impossible to understand what could be causing the issue.
paul c said:
...
I lose coverage so I get the wifi icon with the exclamation mark, instead of it reconnecting automatically. Switching wifi off, then back on, allows me to use wifi again.
I'm using the NX5 AOSP ROM, 5.0R6 (LRX21T)
We all get different experiences, but it sounds like the root cause is likely the same.
Give as much information as you can (Android version, radio, which particular ROM, usage), otherwise it's impossible to understand what could be causing the issue.
Click to expand...
Click to collapse
The same happens on my Nexus 10 (which doesn't have a radio as far as I know) with stock rooted 5.0.
Wi-Fi delayed list...
A very annoying bug that i am facing is when i enable Wi-Fi i have to wait more than two minutes to get the Wi-Fi network list meanwhile i might get messages like "settings are not responding" also none of the new Wi-Fi networks are saved b in to saved network list, so i have to enter wpa keys again and again....
+1
after flashing the factory img, wifi never turns off, there is play services battery drain as well as recent apps bug... fuuck this shyte im going back to kitkat. imho 4.4.4 was stable and battery life was much better.
AJ205 said:
after flashing the factory img, wifi never turns off, there is play services battery drain as well as recent apps bug... fuuck this shyte im going back to kitkat. imho 4.4.4 was stable and battery life was much better.
Click to expand...
Click to collapse
Did you do a clean install or did you just install it over your 4.4?
PoisonWolf said:
Did you do a clean install or did you just install it over your 4.4?
Click to expand...
Click to collapse
once you click "flash all.bat" it formats and cleans everything, so I guess I clean flashed it.
AJ205 said:
once you click "flash all.bat" it formats and cleans everything, so I guess I clean flashed it.
Click to expand...
Click to collapse
I guess I'm just wondering if these are issues are due to not starting a clean slate. I typically try to do a clean wipe of the internal NAND whenever it's a major revision change (4.4 > 5.0).
But if the bugs are persistent for those of you who did a clean install...maybe it's better to hold off for now.
I did a clean flash all as well and have the same issue where WiFi is never turned off. Wtf google. Battery was awesome right before the update
mymeatb18 said:
I did a clean flash all as well and have the same issue where WiFi is never turned off. Wtf google. Battery was awesome right before the update
Click to expand...
Click to collapse
Thanks for the info. I guess I'll hold for now.
as for me, usb tether always turns of itself when i wake/turn the screen on
stock image rooted using CF
wifi works fine
Mine would lose connectivity, meander about for 30 - 60 seconds, and reconnect. I set the WiFi antenna to 2.4Ghz (from Auto) and turned off "Scanning always available" (although I doubt the latter had anything to do with it) and it's been fine ever since. This was on a clean factory install -- no root, no OTA update; pure OEM Lollipop ROM.
Whenever i go to settings > Wifi settings the phone freezes for a couple of seconds and then it crashes. This happens like 70% of the time.
Anyone else having this ?
I dont have any wifi etc problems
Only thing i have noticed so far is the recent apps bug that shows up sometimes
--------------------
Phone: Nexus 4
OS: rooted Lollipop LRX21T
Bootloader: unlocked
stock Recovery
Bluetooth tethering between nexus 4 and nexus 7 breaks every 30 mins or so.
You have to reboot to get it working again.
Decided to take the plunge. Installed lollipop. Am happy to say that I do not have this issue occuring to me though.
yup, wifi issues for me.
Notice it when I get home, my wifi will not connect and when I go to check the settings it has been turned off. So of course I try to turn it on but everything I try does not work, I am unable to get it to turn on. Only a reboot will get wifi working again.
Not happy at all about this. and a couple of other features. Now I'm wishing I never did the update. Google you have taken my expensive smart phone and turned it against me.
pjshark said:
yup, wifi issues for me.
Notice it when I get home, my wifi will not connect and when I go to check the settings it has been turned off. So of course I try to turn it on but everything I try does not work, I am unable to get it to turn on. Only a reboot will get wifi working again.
Not happy at all about this. and a couple of other features. Now I'm wishing I never did the update. Google you have taken my expensive smart phone and turned it against me.
Click to expand...
Click to collapse
It could be a combination of your router and something they've changed in how Lollipop handles networking.
Sicily1918 said:
Mine would lose connectivity, meander about for 30 - 60 seconds, and reconnect. I set the WiFi antenna to 2.4Ghz (from Auto) and turned off "Scanning always available" (although I doubt the latter had anything to do with it) and it's been fine ever since. This was on a clean factory install -- no root, no OTA update; pure OEM Lollipop ROM.
Click to expand...
Click to collapse
I have the same issue. On my Nexus 4, I just set it to 2.4 GHz only, as 5 GHz has never worked since 4.3. I can only connect if I hold the phone up to the router. On my Nexus 7 where 5GHz actually works well, I like the fact it prefers 5GHz.
I was running JDX which is based on the Marshmallow preview and Project Fi was working great without any issues. I recently decided to switch back to a 5.1.1 based ROM due to some other issues on Marshmallow. Since then I have tried both Chroma and Pure Nexus but I keep running into the same issue with Fi. I am able to activate just fine with the Fi app but after awhile I loose mobile data. I stay connected to the network so calls/sms work fine but I get the ! over my network status in the notification bar. A reboot or airplane mode toggle sometimes fixes it. Any ideas on how to permanently fix it or what could be going wrong?
czonin said:
I was running JDX which is based on the Marshmallow preview and Project Fi was working great without any issues. I recently decided to switch back to a 5.1.1 based ROM due to some other issues on Marshmallow. Since then I have tried both Chroma and Pure Nexus but I keep running into the same issue with Fi. I am able to activate just fine with the Fi app but after awhile I loose mobile data. I stay connected to the network so calls/sms work fine but I get the ! over my network status in the notification bar. A reboot or airplane mode toggle sometimes fixes it. Any ideas on how to permanently fix it or what could be going wrong?
Click to expand...
Click to collapse
maybe try flashing a lollipop radio
shelooga said:
maybe try flashing a lollipop radio
Click to expand...
Click to collapse
I thought about that. Which would you suggest?
http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-modem-collection-t2969380
czonin said:
I thought about that. Which would you suggest?
http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-modem-collection-t2969380
Click to expand...
Click to collapse
different ones work in different ways across phones, towers, and netowrks it seems based on the results i see on here usually. i tend to start from the newest first for a day or two, see how it does then downgrade if i see a lot of battery drain or poor signal
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
So ok first off, i really do love this phone. I got it for the camera and for content creation and its great for it...
I had a Redmi note 4 before, and for a couple of years Ive been using a firewall since reading about a lot of chinese phones sending large amounts of data to china.
Now yes my old phone did phone home A LOT. So thats why i installed noroot firewall to keep an eye on things.
And literally every service phoned home. Many services that have no right connecting to the internet.
Now come 10t, i read that because this is an offical EU phone with EU rom and not a grey import, it should be following all the EU rules on data collection... So basically turn everything off it shouldnt contact home.
Trouble is..... even though I have turned most of the things off (outside updating service) many of the apps still phone home... Analytics, MSA DOWNLOADs, file explorer, mi remote, compass, clock security.... and other framework services. All phoning home to servers in china.
Ive not really done a deep dive into exactly what service is sending what data. But Why would downloads connect to a chinese IP every time i download something off the app store.... Or open Chrome?
Well using firewall now to keep things locked down.
Has anyone else seen this kind of activity on EU phones? Is anyone making a clean rom that remove this kind of sus activity?
That's what you have to deal with if you want to use MIUI.
Why not root the phone and flash Lineage?
d3smond said:
That's what you have to deal with if you want to use MIUI.
Why not root the phone and flash Lineage?
Click to expand...
Click to collapse
thats on the cards tbh...
is Lineage fully ported yet? With everything working?
NutsyUK said:
thats on the cards tbh...
is Lineage fully ported yet? With everything working?
Click to expand...
Click to collapse
Yes everything is working except DT2W.
There is minor bugs that will be fixed.
It's very stable.
d3smond said:
Yes everything is working except DT2W.
There is minor bugs that will be fixed.
It's very stable.
Click to expand...
Click to collapse
Some 5ghz wifi bands aren't working
Auto rotate doesn't work
Bluetooth connection to audio devices fails after a call
Screen doesn't wake up when someone calls in like 90% of calls
Lineage Recovery bootloops
And yes dt2w doesn't work. Those are not minor bugs...
calinorg said:
Some 5ghz wifi bands aren't working
Auto rotate doesn't work
Bluetooth connection to audio devices fails after a call
Screen doesn't wake up when someone calls in like 90% of calls
Lineage Recovery bootloops
And yes dt2w doesn't work. Those are not minor bugs...
Click to expand...
Click to collapse
Don't know about 5ghz, I haven't have any issues with 5ghz. It's fixed in the latest version? At least it says so in the notes.
Auto rotation works fine for me. Have't noticed the issue with screen not waking up during incoming calls but I rarely receive or make calls.
I only used my bluetooth in ear for listening to music, not for calls but I se someone wrote it can be fixed by lowering volume a bit.
Lineage recovery bootloops if you flash it to recovery but if you fastboot boot the img it will boot fine every time.
d3smond said:
Don't know about 5ghz, I haven't have any issues with 5ghz. It's fixed in the latest version? At least it says so in the notes.
Auto rotation works fine for me. Have't noticed the issue with screen not waking up during incoming calls but I rarely receive or make calls.
I only used my bluetooth in ear for listening to music, not for calls but I se someone wrote it can be fixed by lowering volume a bit.
Lineage recovery bootloops if you flash it to recovery but if you fastboot boot the img it will boot fine every time.
Click to expand...
Click to collapse
That's all workarounds, that's why I say these are not minor bugs. I had all of those problems. I had 5ghz problem because my wifi router was set to a channel lineage couldn't read. Lowering volume, and turning bluetooth on/off couldn't fix it for me, only restart worked. Auto rotation and blank screen during calls were also my problems. Well to end offtopic, I'll wait for stable pe or similar rom before switching from global rom. I have pihole set up as blocking firewall at home so it helps a ton with phoning home...
ive also tried using noroot firewall, which worked fine on my old phone. but no matter the battery saver settings, it keeps getting shut down by the phone... So thats not secure.
NutsyUK said:
ive also tried using noroot firewall, which worked fine on my old phone. but no matter the battery saver settings, it keeps getting shut down by the phone... So thats not secure.
Click to expand...
Click to collapse
Did you try to turn off MIUI OPTIMIZATION in Developer option?
Developer options? I can't find that...
Ahh found them... Had to enable them first... Been a while forgot about that.