[Q] AOSP LYZ28E & Wi-Fi Calling Issue - Nexus 6 Q&A, Help & Troubleshooting

I need help to figure out how to get Wi-Fi calling to work on AOSP LYZ28E on Nexus 6 and T-Mobile.
I have built many ROMs with AOSP source code from 5.1 on up and have encountered problems with sound & video not working properly with pure source code. I've always been able to find the solutions here on XDA.
With LYZ28E for Nexus 6, a straight build using pure AOSP source code (using repo init, repo sync & make with no additional code) I can't even get a ROM built that has working data on cellular signal.
Straight out of the box on this build, there is no cellular data signal, volume fades, video doesn't work, VoLTE doesn't work & Wi-Fi Calling doesn't work, even though the settings are there.
I've found the solutions for everything except for Wi-Fi Calling. My ROM has a few features added in including Battery & Notification lights, resizable nav bar and battery percentage text, and the sound, video & VoLTE works.
But for the life of me I can't get Wi-Fi calling to work. It works in my house on the factory image so I know it's not a problem with my location or infrastructure settings.
I've looked through the few ROMs here on XDA to compare my code with their Wi-Fi Calling commits, and I can't see any differences. I know I'm missing something, but I can't find it and don't know exactly where to find it. Google searches don't bring up anything useful.
I'm hoping someone here can help point me in the right direction or give me some clues on where to look. I've attached some screen shots of my settings & APN.
I truly appreciate any help you kind folks can provide.
Thanks

from what ive read around, you need to have an edited kernel, with the proper edits, to get wifi calling to work on aosp. what are the edits, i dont know, but it needs to be done. you can look at chroma roms source code to look what was done to get wifi calling to work.

Thanks simms, I saw ZephiK had some kennel work in his Git, so I'll look into that and see what I can do from there.
Thank you very much for the tip!

good luck!

Thanks I'm going to download his kernel source and try to figure out if I can stick it into my files and see if it builds or if I need to compile it separately or whatever needs to be done haha
I'll update this thread with the results...
Onward and upwards
EDIT: I managed to finally get wifi calling to work on my rom, thanks to Pure Nexus ROM source. It turns out the AOSP stock kernel does enable wfc out of the box. There's just a lot of proprietary vendor files I didn't have that I obtained from the Pure Nexus source.
So, yeah, finally got everything working on my rom that I want

Related

[Q] Quest for stock-like ROM for UK and instructions

Hi,
Can anybody suggest a ROM that will work well in the UK, and provides a stock-like experience with a reasonably up to date version of Android. It doesn't have to be bleeding edge - I'd rather have everything working rather than access to the very latest features.
I've currently got a stock ICS, and so wonder if somebody could point me to easy step by step instructions on how to flash the suggested ROM. There's a lot of jargon about safe straps, and so on, and some of the instructions seem to expect a level of knowledge that I don't have (I'm happy to learn if somebody would be good enough to point me in the direction of some documentation).
It's not that I'm overly unhappy with the stock ICS, but there are a few things that aren't working that well for me (MMS, Hotspot, etc) and an annoyance or two (unknown sim source message, and unnecessary Verizon apps) that are making me think I should re-flash to something cleaner.
Cheers,
Steve.
StevePritchard said:
Hi,
Can anybody suggest a ROM that will work well in the UK, and provides a stock-like experience with a reasonably up to date version of Android. It doesn't have to be bleeding edge - I'd rather have everything working rather than access to the very latest features.
I've currently got a stock ICS, and so wonder if somebody could point me to easy step by step instructions on how to flash the suggested ROM. There's a lot of jargon about safe straps, and so on, and some of the instructions seem to expect a level of knowledge that I don't have (I'm happy to learn if somebody would be good enough to point me in the direction of some documentation).
It's not that I'm overly unhappy with the stock ICS, but there are a few things that aren't working that well for me (MMS, Hotspot, etc) and an annoyance or two (unknown sim source message, and unnecessary Verizon apps) that are making me think I should re-flash to something cleaner.
Cheers,
Steve.
Click to expand...
Click to collapse
MMS and hotspot are easy to fix.
I'm not sure who your carrier is, but make sure your APN has MMS in it. When it comes to Hotspot, find my thread on enabling hotspot to work on Rogers wireless, it should give you some ideas. It involves you disabling the entitlement check and then adding (through the same program) a DUN apn type which allows for wireless hotspot to function properly.
I just find ICS slow, and I've loaded up Hashcode's CM10 port. Working pretty well so far, but I do miss a few things about blur.
danifunker said:
MMS and hotspot are easy to fix.
I'm not sure who your carrier is, but make sure your APN has MMS in it. When it comes to Hotspot, find my thread on enabling hotspot to work on Rogers wireless, it should give you some ideas. It involves you disabling the entitlement check and then adding (through the same program) a DUN apn type which allows for wireless hotspot to function properly.
I just find ICS slow, and I've loaded up Hashcode's CM10 port. Working pretty well so far, but I do miss a few things about blur.
Click to expand...
Click to collapse
Thanks - I've rooted now, and managed to get the hotspot working (I think, it's untested, but it at least runs now). I've also got MMS working, which turned out to be a Handcent problem, although the only reason I have Handcent is that stock simply won't work, which is really confusing, because you would expect them to use the same settings.
I also have got rid of the semi-annoying "sim card from an unknown source" message too, and because the phone is rooted, I can get it to reboot daily automatically, which I think will probably help with some of the other weird behaviours I occasionally see.
I guess this has taken the pressure off flashing something new, but if there is a stock-like Jelly Bean ROM then I could be tempted. Presumably because I've rooted, when the official JB comes I'll have to do something special to get it to install, but I guess that will be half the fun.
Cheers,
Steve.

Droid 3 XT860 gsm/XT862

JUST A WARNING! if you attempt this i will not be held accountable for any issues. you have been warned!
Long story short, looking for roms to try. i found this while searching http://d-h.st/Ici, [Liquidsmoothv3.0 4.4.2 Kitkat] No camera, not sure on other issues!
I downloaded it and it runs rather well, a few hiccups. it seems to run only on GSM though, but i could be wrong. if needed i could upload a few pictures to thread. however ( i know this is the case with some gb roms with gsm fixes, same with ics and jellybean, as needed with build.prop tweaks) but for the life of me cannot get gsm to activate data, it can receive and make calls, send sms. it doesnt seem to like saving apns, theres a mod called
http://www.internauta37.altervista.org/how-and-patch-fully-enable-gsm-verizon-cdma-phones-android
it lets me save apns, but if i add to many things. the apn doesnt save. but if i out the basic info i need to activate data on any other rom, it doesnt activate at all. if anyone tries this and gets data working. please let me know! goodluck
LiL_Assassin said:
JUST A WARNING! if you attempt this i will not be held accountable for any issues. you have been warned!
Long story short, looking for roms to try. i found this while searching http://d-h.st/Ici, [Liquidsmoothv3.0 4.4.2 Kitkat] No camera, not sure on other issues!
I downloaded it and it runs rather well, a few hiccups. it seems to run only on GSM though, but i could be wrong. if needed i could upload a few pictures to thread. however ( i know this is the case with some gb roms with gsm fixes, same with ics and jellybean, as needed with build.prop tweaks) but for the life of me cannot get gsm to activate data, it can receive and make calls, send sms. it doesnt seem to like saving apns, theres a mod called
http://www.internauta37.altervista.org/how-and-patch-fully-enable-gsm-verizon-cdma-phones-android
it lets me save apns, but if i add to many things. the apn doesnt save. but if i out the basic info i need to activate data on any other rom, it doesnt activate at all. if anyone tries this and gets data working. please let me know! goodluck
Click to expand...
Click to collapse
There is a thread for that rom http://forum.xda-developers.com/showthread.php?t=2674609&page=3
I just added a wifi fix to the rom, I never tried 3g just wifi.
sd_shadow said:
There is a thread for that rom http://forum.xda-developers.com/showthread.php?t=2674609&page=3
I just added a wifi fix to the rom, I never tried 3g just wifi.
Click to expand...
Click to collapse
Hey mate, i know. im sorry i should have quoted you on that fact, Wifi works really well. I dont suppose you could take a look at the 3g/data. i could help debug it if you need to. as weird as it sounds, its a really smooth rom, no pun intended lol. every other rom i have tried lags :/

[Q] WiFi calling on AOSP on Project Fi

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.

[ROM][5.1.1][UNOFFICIAL] AICP v10.0 for m7spr [10.3.2015]

UNOFFICIAL AICP for the Sprint HTC One​
Since @superfes is no longer using this phone, I figured I would post some unofficial builds of AICP (Android Ice Cold Project). The previous thread is intended for closure, so we can use this one. To be clear, I'm only compiling this ROM and will not be troubleshooting specific issues. I will do my best to troubleshoot, but no guarantees. Any help on this front is appreciated - I'm new to this and am interested in continuing to learn.
I'm planning on putting together a build once every week or two for personal use and will share that with you guys.
Obligatory disclaimer: I am not responsible for any trouble you may run into with flashing or otherwise using this ROM. Just because it is working well for me does not guarantee that you will have the same experience.
For those of you wondering what AICP is: http://aicp-rom.com
Download link
10/3/2015: Google drive: https://drive.google.com/open?id=0B0lza8kzVL9RSVNnUzdoT0J5QWs
Build notes
10/3/2015
- Fresh build from 10/3
- Tested service / data when moving and no issues
- Remember that I am not troubleshooting specific issues. I'm not a developer. If you wish to post a logcat or anything like that though, feel free and I will take a look but not necessarily be able to provide a solution
- Yes, the digital roaming display is still there. In fact, when you see digital roaming, this is a sign that you are in service. 'Sprint' shows up when you are roaming so it is backwards.
9/27/2015:
- Didn't make clobber so build that hasn't been updated since 9/19 does not show an update (i.e. build will say 9/19 in many places since that was my last full repo sync). For future builds I will do this but didn't feel like waiting that many hours today
- Cherry-picked tdhite's commit from PAC ROM: http://review.pac-rom.com/#/c/13403/
------This has fixed the com.android.phone crashing problem + service being dropped
------ Usable as a daily driver again!
- From a full day on this ROM it's running smoothly and without errors
- 'Digital Roaming' display-only issue persists (been there for a long time now - no surprises here), and it is not indicative of actually roaming. Go into settings / about / sim status to definitively determine what your service status is.
Reserved
Reserved for now
Appreciate any feedback you guys have too
I'll give it a try and let you know.
Sent from my One using Tapatalk
wmatheney said:
I'll give it a try and let you know.
Sent from my One using Tapatalk
Click to expand...
Click to collapse
I couldn't get a solid connection. It was roaming and when I toggled the network type to global, I lost connectivity. I toggled back to CDMA/LTE but still no connection. I toggled Airplane mode. Still no go. I then changed it to Global and got a connection finally, but it was still roaming.
I hope this helps.
Sent from my One using Tapatalk
Same issue I've noticed everywhere, no proximity sensor feedback when in dialer!
I'm not pushing the power button every time I get called or I make a call. Only reason I'm still glued to 4.4.4.
Tjis is my 3rd m7 on kk and lp Ota, all 3 on both revisions, same issue.
Sent from my One using Tapatalk
wmatheney said:
I couldn't get a solid connection. It was roaming and when I toggled the network type to global, I lost connectivity. I toggled back to CDMA/LTE but still no connection. I toggled Airplane mode. Still no go. I then changed it to Global and got a connection finally, but it was still roaming.
I hope this helps.
Sent from my One using Tapatalk
Click to expand...
Click to collapse
The digital roaming issue is cosmetic - that one's to be expected (see build notes; you are probably not roaming). As for the connectivity drop, I haven't run into that. If that's happening infrequently and you can deal with the display issue, this ROM should be otherwise fine for service-related actions (calls/texts) in my experience over the last couple of days.
swerff said:
Same issue I've noticed everywhere, no proximity sensor feedback when in dialer!
I'm not pushing the power button every time I get called or I make a call. Only reason I'm still glued to 4.4.4.
Tjis is my 3rd m7 on kk and lp Ota, all 3 on both revisions, same issue.
Sent from my One using Tapatalk
Click to expand...
Click to collapse
Yes, that one is pretty annoying. I have also noticed it on AOSP LP ROMs including this one and just deal with it. Sorry to hear that's holding you back. If there's a fix out there and I come across it, I'll be sure post about it and add to the ROM if applicable.
You can port camera stock m7?
http://www.apkmirror.com/apk/htc-co.../htc-camera-7-30-581119-android-apk-download/
Vember31 said:
Yes, that one is pretty annoying. I have also noticed it on AOSP LP ROMs including this one and just deal with it. Sorry to hear that's holding you back. If there's a fix out there and I come across it, I'll be sure post about it and add to the ROM if applicable.
Click to expand...
Click to collapse
Do you need a log cat when doing anything? Sensor programs show the proximity responding as expected.
Sent from my One using Tapatalk
First of all, great ROM! Have used AICP on my Nexus 4 and my TF300T in the past and it's always been a nice, stable ROM. Just got one question about non-market apps. I've been unable to install any, though I do have the option enabled in the Security menu. From what I've been able to tell, I can start the install of non-market apks with no problem but then the install screen closes by itself and once or twice, I've seen a pop-up that says something about Anti-piracy software activated. Is there any way around this?
So I need Gapps with this ROM?
How about MM?
Any aicp work?
Sent from my One using Tapatalk
Just wanted to stop in and say thank you for uploading this to the site. I have had a hard time finding a good daily driver and this is perfect for my needs.
If you are still building weekly for your own personal use i would greatly appreciate you uploading here as well.
Also I like the inclusion of more cpu governors such as smartmax_eps, has been great for pokemon go

Am I the Only One with Trouble Tethering After Switch from Nougat to Oreo or Pie?

Tether was working fine on Nougat, after adjusting Windows with TTL, a changed user-agent, etc., and then in Android adding the "dun" parameter to my APN, but with any Oreo or Pie ROM, it gets incredibly slow, as if I do not have "dun" in my APN, even when using ROMs that allow "dun" in APN.
I'd really like to upgrade from Nougat, but don't want to give up tether.
Has anyone else faced this issue and prevailed?
EDIT:
I flashed OOS Oreo, tried what settings I could with no good results, then flashed 4.5.1 firmware and modem into it to see if older firmware was the solution, tried what settings I could to no avail.
Back on Nougat now, which does the job just fine.
Alas however, I may never be able to buy a new phone, unless Nougat can be installed onto it.
You're certainly not the only one. Tethering support is getting harder as carriers find ways of making it more restricted. There are ROMs and Devs that have worked on it with mixed results. It's possible with enough leg work you might get it working on a particular ROM, if you can get the dev to work with you on it. Otherwise it's luck of the draw whether you can find a ROM that will work in your particular case.
Telephony is getting complicated and there are more people concerned with VoLTE and the like. Look what a mess that still is on custom ROMs.
Does anyone know of any ROMs where this is actively being fixed? That is, one can tether without degradation, as one used to be able to do in Nougat? Tethering works, it's just horribly slow.
pbergonzi said:
Does anyone know of any ROMs where this is actively being fixed? That is, one can tether without degradation, as one used to be able to do in Nougat? Tethering works, it's just horribly slow.
Click to expand...
Click to collapse
NLOS is your best bet. If it's not working already the dev is willing to work with users to resolve issues.
Here's an example of Tethering restrictions getting worse, with Google leading the charge:
https://www.reddit.com/r/Android/comments/9r6r13/tether_dun_required_no_longer_works_on_pixel_3_xl/
I'm surprised Google don't get whiplash in their haste to bow to pressure from US Carriers.
Dirk said:
NLOS is your best bet. If it's not working already the dev is willing to work with users to resolve issues.
Here's an example of Tethering restrictions getting worse, with Google leading the charge:
https://www.reddit.com/r/Android/comments/9r6r13/tether_dun_required_no_longer_works_on_pixel_3_xl/
I'm surprised Google don't get whiplash in their haste to bow to pressure from US Carriers.
Click to expand...
Click to collapse
Thank you @Dirk, and agreed--I'm surprised google doesn't get backlash--maybe not enough people tether?
Also surprised that more devs didn't just immediately address that--maybe not enough devs tether?
I may try NLOS, or the Magisk module--it might work.
Does anyone using NLOS know if tether works properly? I will ask in that thread also.

Categories

Resources