Database Develop

Flurry agent, sending out data!!!

I saw something in my logcat about "Flurry Agent" sending out data to its server. It looks like it collects analytics about certain apps and uploads it.
Does anyone know how to remove/disable this?
A hosts file addition is one way.
Some google search results:
Flurry-Legal
flurry-legal-dcma
Comes with Locale. (I don't have locale installed anymore, yet Flurry was running)
A search on my phone turned up nothing. It may be a library inside an apk.
find / -name "*lurry*"

I've added these line to my hosts file ( /etc/hosts )
127.0.0.1 data.flurry.com
127.0.0.1 flurry.com
127.0.0.1 dev.flurry.com
The below data shows up on the dashboard once flury is added to an app.
Application The name of the application.
New Users The number of new users who used the application for the first time during the specified time period.
Active Users The number of unique users who used the application during the last complete week of the specified time period.
Sessions The total number of user sessions that occurred during the specified time period.
Weekly Growth The percentage increase of new users between the last two complete weeks of the specified time period.
User Retention The percent of users that signed up during the time period have used the app during the last 7 days before today.
Click to expand...
Click to collapse
Also:
Device Model,
Firmware,
Carrier,
Location,
Errors and Exceptions,
Custom 'Events'.

Omg man i just noticed the same thing and was about to post!! I have no idea what app it is though because I don't have locale installed

It could be inside any app you have. Flurry is a company that collect statistics on app usage afaik and developers add the library to their apps. Don't know how widespread it is for developers to do this though.

SBS_ said:
It could be inside any app you have. Flurry is a company that collect statistics on app usage afaik and developers add the library to their apps. Don't know how widespread it is for developers to do this though.
Click to expand...
Click to collapse
Yes I figured that out and even downloaded the sdk.
Found out that BetterTermEmulator pro uses this and sends an error report whenever it crashes.
Code:
I/BetterTermEmulator( 3440): Command: '/system/bin/sh logcat'
I/BetterTermEmulator( 3440): chdir() to '/'
I/BetterTermEmulator( 3440): title is: 'BTEP'
I/BetterTermEmulator( 3440): Starting subprocess '/system/bin/sh logcat null'
I/BetterTermEmulator( 3440): waiting for: 463
D/FlurryAgent( 3440): Starting new session
D/NetworkLocationProvider( 141): addListener(): com.magicandroidapps.bettertermpro
D/NetworkLocationProvider( 141): setMinTime: 0
D/WifiService( 141): acquireWifiLockLocked: WifiLock{NetworkLocationProvider type=2 [email protected]}
D/FlurryAgent( 3440): Sending report to: http://data.flurry.com/aar.do
I/BetterTermEmulator( 3440): Subprocess exited: 2
I/NotificationService( 141): enqueueToast pkg=com.magicandroidapps.bettertermpro [email protected] duration=0
I/BetterTermEmulator( 3440): Subprocesses exited with code 2
E/BetterTermEmulator( 3440): onSizeChanged: W:480 H:762old W:0H:0
D/FlurryAgent( 3440): Ending session
D/LocationManager( 3440): removeUpdates: listener = [email protected]
D/NetworkLocationProvider( 141): removeListener(): com.magicandroidapps.bettertermpro

I use the custom hosts file found over in android app, gonna have to open that up and addd them in if its not already there.

I just noticed this too while working with the Eclipse IDE DDMS and logcat views. Edited my /etc/hosts as well.

for info: the AdFree application is adding these lines to the hosts file

[Q] Feint?

Has anybody gotten Feint to load properly? All I get is endless "loading Feint" and I have to press the Back button to get to the game.

Came here to post this - works sometimes, not others. If no one has done so yet, I'll try getting a log cat later to see if I can figure out why, but it's probably a missing part of the OS.

I've actually engaged OpenFeint themselves through their support and they've been as helpful as they can be considering it isn't an officially supported device. Here's what I got.
My LogCat is attached which they requested and actually looked at.
Here's what the thread looks like.
Is there any chance you could tell me what other resources feint depends on? I know you can call resources from other apps so feint must require something that isn't available on the Nook Color's version of Android.
Feb-04 2011 13:08
Erwin
OpenFeint
Hi,
Feint depends web-related components such as webView and Apache...so if the Nook version doesn't have it it will error out.
-Erwin
Regards,
Erwin
Feb-04 2011 16:22
Tekchip
Odd, I know the NC has a Browser.apk installed. It's not clear if it's the original or not so that shouldn't be the problem. I don't recall seeing an org.apache.http but it must have one as the Android docs http://developer.android.com/reference/org/apache/http/package-descr.html indicate it's necessary for http communication to happen at all. Ideas? Is there anything I can run/do to gather more information about the problem?
Feb-04 2011 16:32
Tekchip
I see webView is a default function with in Android so if it's running android, and has a browser it should have webview. I imagine the hang up is on this Apache piece. Doing a quick search I found a package called org.apache.http. It appears to be a package but I don't find any apks out there. I also don't see an installed apache APK's on my phone(droid 1 running 2.3).
Feb-04 2011 16:42
Erwin
OpenFeint
Hi,
We'll take a look to see how it works but we currently don't support the device so there are no guarantees. Let me know if you need help with anything else.
-Erwin
Regards,
Erwin
Feb-04 2011 17:21
Erwin
OpenFeint
Can you connect it to a computer with the Android dev tools installed, run the Feint Game Spotlight app up until it hangs, and run adb logcat on a connected computer and send the output?
Regards,
Erwin
Feb-05 2011 07:49
Tekchip
I do have adb access to do that however I am out of town with nothing but my mobile available so I won't be able to get that info for you until 7 Feb.
Feb-05 2011 12:59
Tekchip
Here is the log cat from running Feint Game Spotlight. I captured this using a logcat app that has some settings to get more fine grained information so hopefully it didn't exclude anything important. I couldn't get it to replicate but earlier on I saw an error that indicated a cache directory could not be created. From there on it throws this set of errors that appear is if it's simply timing out. I'm going to try to re-create the original logcat entry I saw that in.
W/InputManagerService( 836): Window already focused, ignoring focus gain of: [email protected]
I/ActivityManager( 836): Starting activity: Intent { act=com.encore.intent.action.jump flg=0x14400000 cmp=com.bn.nook.applauncher/.jump.JumpActivity }
V/alogcat ( 8979): save instance
V/alogcat ( 8979): paused
D/DeviceManagerBroadcastReceiver( 1070): action (com.bn.devicemanager.ACTION_DEVICE_USAGE)
I/DeviceManagerHandler( 1070): HandleMessage(): msg.what (7)
I/ActivityManager( 836): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.aurorafeint.spotlight/.SpotlightActivity }
V/WebUI ( 7963): --- WebUI Bootup ---
V/WebUI ( 7963): Loading URL: file:///data/data/com.aurorafeint.spotlight/files/webui/index.html
W/InputManagerService( 836): Starting input on non-focused client [email protected] (uid=10002 pid=1398)
I/ActivityManager( 836): Displayed activity com.aurorafeint.spotlight/.SpotlightActivity: 1548 ms (total 3033 ms)
D/alogcat ( 8979): stopping ...
W/InputManagerService( 836): Window already focused, ignoring focus gain of: [email protected]
D/alogcat ( 8979): stopped
D/WindowManager( 836): interceptKeyTi code=4 down=true repeatCount=0 keyguardOn=false mHomePressed=false
D/WindowManager( 836): interceptKeyTi code=4 down=false repeatCount=0 keyguardOn=false mHomePressed=false
I/NotificationService( 836): enqueueToast pkg=org.jtb.alogcat [email protected] duration=1
D/alogcat ( 8979): stopping ...
D/alogcat ( 8979): starting ...
D/alogcat ( 8979): canceling periodic saves
V/alogcat ( 8979): started
V/alogcat ( 8979): resumed
D/dalvikvm( 8979): GC freed 2923 objects / 399720 bytes in 131ms
D/webviewglue( 7963): nativeDestroy view: 0x422cd0
D/dalvikvm( 7963): GC freed 4907 objects / 509912 bytes in 100ms
D/dalvikvm( 1398): GC freed 920 objects / 65960 bytes in 144ms
D/WifiService( 836): ACTION_BATTERY_CHANGED pluggedType: 0
D/DeviceManagerBroadcastReceiver( 1070): action (android.intent.action.BATTERY_CHANGED)
D/twcCurrentConditions( 1249): updateLoc:52002
D/twcCurrentConditions( 1249): no need to pull any data:52002
D/WifiService( 836): ACTION_BATTERY_CHANGED pluggedType: 0
D/DeviceManagerBroadcastReceiver( 1070): action (android.intent.action.BATTERY_CHANGED)
D/WindowManager( 836): interceptKeyTi code=82 down=true repeatCount=0 keyguardOn=false mHomePressed=false
D/WindowManager( 836): interceptKeyTi code=82 down=false repeatCount=0 keyguardOn=false mHomePressed=false
Feb-09 2011 08:27
Erwin
OpenFeint
Hi,
We couldn't find anything obvious from the log output so we'll need to get our hands on a device to check it out. Thanks for the info!
Regards,
Erwin
Feb-09 2011 10:26
Tekchip
Erwin,
I don't think the logcat app I used had the right filtering. I'm going to try to get it hooked up to my PC with real ADB access and do a raw logcat. Been busy lately so I had to try to use the shortcut method to get some output. I'll drop the info as soon as I get it. I appreciate your patience in working with me!
Brock
Feb-09 2011 10:45
Tekchip
Got it! This shows everything and it appears to be obvious where the problems are. I can't decipher it my self but some things are not able to be loaded etc. and it can't seem to locate the sdcard. I hope this helps!
logcat.txt
Feb-09 2011 13:38
Erwin
OpenFeint
Here's the latest on that from our Android guru:
So, the 'unable to access /sdcard' is actually expected, and doesn't indicate a problem...
However, the "unable to create webviewCache directory" is something I haven't seen before. That error message is actually coming from Android OS instead of our code. I've googled around a bit and it looks like this seems to happen on some rooted devices when they open the Browser. Most of the hits I'm finding are from the HTC Desire. Here is a quote from the only person I can find who seems to have fixed it:
"EDIT: Update - now fixed after repairing ext filesystem on the sdcard and repairing uid permissions from the receovery partition."
Hope that helps
Regards,
Erwin
Feb-09 2011 14:06
Erwin
OpenFeint
Google: 'fix apk uid permissions' in amonra recovery
That might help/might not...but keep in mind we can't officially support
Regards,
Erwin
Feb-09 2011 14:19
It looks like the red highlighted text is the fix. I haven't had a chance to try it using Amonra's recovery. I did try a fix permissions from clockwork but to no avail.

So has anyone had any luck with this or is feint working for most people with 1.1.0 stock rooted?
I have't tried logcat yet, but I did try CWM's permission fix, but still no go.

HBO GO

I'm surprised no one has hacked. This app to make it work on the xoom.
Sent from my SPH-D700 using XDA Premium App

Indeed, I am surprised as well, how has this not been hacked yet?

Just getting ready to start a thread about this. it works on the Evo, Evo 3D and my Galaxy Tab. Now that I have a Xoom too, it doesn't work. What's the problems is it the resolution?

I have it on my vibrant. Works GREAT!!!
Sent from my SGH-T959 using XDA Premium App

MikeJennni said:
I have it on my vibrant. Works GREAT!!!
Sent from my SGH-T959 using XDA Premium App
Click to expand...
Click to collapse
That's wonderful, but what about our Xooms?

it's a combination of honeycomb and the tegra processor. same goes for netflix.

patass said:
it's a combination of honeycomb and the tegra processor. same goes for netflix.
Click to expand...
Click to collapse
Wow. Are any other Honeycombs tablets able to run it?

shaun0207 said:
Wow. Are any other Honeycombs tablets able to run it?
Click to expand...
Click to collapse
No
Sent from my Nexus S 4G using Tapatalk

patass said:
it's a combination of honeycomb and the tegra processor. same goes for netflix.
Click to expand...
Click to collapse
Are you sure it is just that there's no copy protection or whatever bull**** built-in? I might take a crack at this, anyway.

jondwillis said:
Are you sure it is just that there's no copy protection or whatever bull**** built-in? I might take a crack at this, anyway.
Click to expand...
Click to collapse
Let me reiterate, this app works on my locked bootloader droidx but doesn't work anymore on my sisters Droid 1 with the same gpu. It used to work, but they disabled it recently, if my sister is to be trusted.

There is a very easy to have HBO go on ur zoom. Provided you have a subscription to HBO obviously. OK go to your android browser on the zoom. In the address bar type this. About:debug. Hit enter. Nothing will really happen go to settings in top right corner of browser. You should see the word debug. Click that. Find UAString. Click it and choose desktop..DO NOT RESTART BROWSER just got HBOgo.com and instead of asking u what device u have it will bring you to the desktop version where u enter your subscription info and then have at it. Just like on your desktop. And it is smooth and quick just as good as our apps
Sent from my Xoom using XDA App

chrism0483 said:
There is a very easy to have HBO go on ur zoom. Provided you have a subscription to HBO obviously. OK go to your android browser on the zoom. In the address bar type this. About:debug. Hit enter. Nothing will really happen go to settings in top right corner of browser. You should see the word debug. Click that. Find UAString. Click it and choose desktop..DO NOT RESTART BROWSER just got HBOgo.com and instead of asking u what device u have it will bring you to the desktop version where u enter your subscription info and then have at it. Just like on your desktop. And it is smooth and quick just as good as our apps
Sent from my Xoom using XDA App
Click to expand...
Click to collapse
Oh sure, the flash site works, but it is hard to use and I always notice choppiness when it starts sending high quality video. (the video quality adapts with connection speed)

Update!
I took a look at the APK and was able to bypass their device check, login to my account, and even get the short HBO logo video to play, and then a FC.
The logcat looks like this:
Code:
07-22 03:28:22.421: ERROR/AndroidRuntime(2382): java.lang.NoSuchFieldError: no field with name='mSurface' signature='I' in class Landroid/view/Surface;
07-22 03:28:22.421: ERROR/AndroidRuntime(2382): at com.nextreaming.nexplayerengine.NexPlayer._Constructor(Native Method)
07-22 03:28:22.421: ERROR/AndroidRuntime(2382): at com.nextreaming.nexplayerengine.NexPlayer.init(NexPlayer.java:1410)
07-22 03:28:22.421: ERROR/AndroidRuntime(2382): at com.HBO.Service.NexPlayerService.getNexPlayerGuard(NexPlayerService.java:54)
07-22 03:28:22.421: ERROR/AndroidRuntime(2382): at com.HBO.PlayMediaNexPlayerActivity.playActualVideo(PlayMediaNexPlayerActivity.java:446)
07-22 03:28:22.421: ERROR/AndroidRuntime(2382): at com.HBO.PlayMediaNexPlayerActivity.access$8(PlayMediaNexPlayerActivity.java:418)
07-22 03:28:22.421: ERROR/AndroidRuntime(2382): at com.HBO.PlayMediaNexPlayerActivity$5.handleMessage(PlayMediaNexPlayerActivity.java:266)
07-22 03:28:22.421: ERROR/AndroidRuntime(2382): at android.os.Handler.dispatchMessage(Handler.java:99)
07-22 03:28:22.421: ERROR/AndroidRuntime(2382): at android.os.Looper.loop(Looper.java:132)
07-22 03:28:22.421: ERROR/AndroidRuntime(2382): at android.app.ActivityThread.main(ActivityThread.java:4025)
07-22 03:28:22.421: ERROR/AndroidRuntime(2382): at java.lang.reflect.Method.invokeNative(Native Method)
07-22 03:28:22.421: ERROR/AndroidRuntime(2382): at java.lang.reflect.Method.invoke(Method.java:491)
07-22 03:28:22.421: ERROR/AndroidRuntime(2382): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:841)
07-22 03:28:22.421: ERROR/AndroidRuntime(2382): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:599)
07-22 03:28:22.421: ERROR/AndroidRuntime(2382): at dalvik.system.NativeStart.main(Native Method)
I'll delve a little further tomorrow, but I'm optimistic since it was very, very easy to bypass their device checks.
Edit) I can't watch anything for awhile since the crash has caused my HBO GO ID to be locked into streaming something, but I'll post the APK here.

much appreciated Jon

jondwillis said:
Update!
I took a look at the APK and was able to bypass their device check, login to my account, and even get the short HBO logo video to play, and then a FC.
The logcat looks like this:
Code:
07-22 03:28:22.421: ERROR/AndroidRuntime(2382): java.lang.NoSuchFieldError: no field with name='mSurface' signature='I' in class Landroid/view/Surface;
07-22 03:28:22.421: ERROR/AndroidRuntime(2382): at com.nextreaming.nexplayerengine.NexPlayer._Constructor(Native Method)
07-22 03:28:22.421: ERROR/AndroidRuntime(2382): at com.nextreaming.nexplayerengine.NexPlayer.init(NexPlayer.java:1410)
07-22 03:28:22.421: ERROR/AndroidRuntime(2382): at com.HBO.Service.NexPlayerService.getNexPlayerGuard(NexPlayerService.java:54)
07-22 03:28:22.421: ERROR/AndroidRuntime(2382): at com.HBO.PlayMediaNexPlayerActivity.playActualVideo(PlayMediaNexPlayerActivity.java:446)
07-22 03:28:22.421: ERROR/AndroidRuntime(2382): at com.HBO.PlayMediaNexPlayerActivity.access$8(PlayMediaNexPlayerActivity.java:418)
07-22 03:28:22.421: ERROR/AndroidRuntime(2382): at com.HBO.PlayMediaNexPlayerActivity$5.handleMessage(PlayMediaNexPlayerActivity.java:266)
07-22 03:28:22.421: ERROR/AndroidRuntime(2382): at android.os.Handler.dispatchMessage(Handler.java:99)
07-22 03:28:22.421: ERROR/AndroidRuntime(2382): at android.os.Looper.loop(Looper.java:132)
07-22 03:28:22.421: ERROR/AndroidRuntime(2382): at android.app.ActivityThread.main(ActivityThread.java:4025)
07-22 03:28:22.421: ERROR/AndroidRuntime(2382): at java.lang.reflect.Method.invokeNative(Native Method)
07-22 03:28:22.421: ERROR/AndroidRuntime(2382): at java.lang.reflect.Method.invoke(Method.java:491)
07-22 03:28:22.421: ERROR/AndroidRuntime(2382): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:841)
07-22 03:28:22.421: ERROR/AndroidRuntime(2382): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:599)
07-22 03:28:22.421: ERROR/AndroidRuntime(2382): at dalvik.system.NativeStart.main(Native Method)
I'll delve a little further tomorrow, but I'm optimistic since it was very, very easy to bypass their device checks.
Edit) I can't watch anything for awhile since the crash has caused my HBO GO ID to be locked into streaming something, but I'll post the APK here.
Click to expand...
Click to collapse
OUTSTANDING! Thank you so much for looking into this

To be clear, I'm not yet certain if the playback FC is happening because I'm skipping some DRM/device checks, or because of a hardware incompatibility.
Edit) I sideloaded the modified apk on my droid x, which handles the regular hbogo app just fine normally. At first when I tried to watch something, the screen flashed black for a split second and then returned me to the previous screen. After closing the app and signing in again, I was able to get playback working just fine. Seems like it could be an incompatibility after all.

So if you know how to remove device checks can you give hulu plus a crack. I can post the apk if you need it.
Sent from my Xoom using XDA Premium App

B Dizzle said:
So if you know how to remove device checks can you give hulu plus a crack. I can post the apk if you need it.
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
Hey, let's not call these cracks... more like... enablers. But I can take a crack at it, even though its probably not as easy as the HBO GO one.

Nice! The only thing missing is Hulu. HBO would be icing on the cake with Netflix and Hulu up and running.
Sent from my Xoom using XDA Premium App

jondwillis said:
Update!
I took a look at the APK and was able to bypass their device check, login to my account, and even get the short HBO logo video to play, and then a FC.
The logcat looks like this:
Code:
07-22 03:28:22.421: ERROR/AndroidRuntime(2382): java.lang.NoSuchFieldError: no field with name='mSurface' signature='I' in class Landroid/view/Surface;
07-22 03:28:22.421: ERROR/AndroidRuntime(2382): at com.nextreaming.nexplayerengine.NexPlayer._Constructor(Native Method)
07-22 03:28:22.421: ERROR/AndroidRuntime(2382): at com.nextreaming.nexplayerengine.NexPlayer.init(NexPlayer.java:1410)
07-22 03:28:22.421: ERROR/AndroidRuntime(2382): at com.HBO.Service.NexPlayerService.getNexPlayerGuard(NexPlayerService.java:54)
07-22 03:28:22.421: ERROR/AndroidRuntime(2382): at com.HBO.PlayMediaNexPlayerActivity.playActualVideo(PlayMediaNexPlayerActivity.java:446)
07-22 03:28:22.421: ERROR/AndroidRuntime(2382): at com.HBO.PlayMediaNexPlayerActivity.access$8(PlayMediaNexPlayerActivity.java:418)
07-22 03:28:22.421: ERROR/AndroidRuntime(2382): at com.HBO.PlayMediaNexPlayerActivity$5.handleMessage(PlayMediaNexPlayerActivity.java:266)
07-22 03:28:22.421: ERROR/AndroidRuntime(2382): at android.os.Handler.dispatchMessage(Handler.java:99)
07-22 03:28:22.421: ERROR/AndroidRuntime(2382): at android.os.Looper.loop(Looper.java:132)
07-22 03:28:22.421: ERROR/AndroidRuntime(2382): at android.app.ActivityThread.main(ActivityThread.java:4025)
07-22 03:28:22.421: ERROR/AndroidRuntime(2382): at java.lang.reflect.Method.invokeNative(Native Method)
07-22 03:28:22.421: ERROR/AndroidRuntime(2382): at java.lang.reflect.Method.invoke(Method.java:491)
07-22 03:28:22.421: ERROR/AndroidRuntime(2382): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:841)
07-22 03:28:22.421: ERROR/AndroidRuntime(2382): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:599)
07-22 03:28:22.421: ERROR/AndroidRuntime(2382): at dalvik.system.NativeStart.main(Native Method)
I'll delve a little further tomorrow, but I'm optimistic since it was very, very easy to bypass their device checks.
Edit) I can't watch anything for awhile since the crash has caused my HBO GO ID to be locked into streaming something, but I'll post the APK here.
Click to expand...
Click to collapse
Is there a chance this will lock our device or HBO GO ID to be locked?

Let's fix up CM10.1 (bugs + discussion)

Again: No chitchat, no "thank you" posts, no non-technical questions, no bug reports without logcats.
As the other CM10.1 threads usually are overrun by users let's try to make use of the new section and create a new bug thread in here.
Bug reports including a clear description and a logcat are welcome, every offtopic post will get deleted. Simple as that :fingers-crossed:
This thread can get used for discussion of these bugs as well - as long as it's closely development focused (e.g. "based on the logcat the problem is in package xyz, here's my idea how to fix it").
We have created a github organization where we'll push the fixes (and commit them to Gerrit if @aremcee is still interested at maintaining the P990 ).
https://github.com/p990-dev
If you want to help just send a pull request (or PM me about getting full access).
There are dedicated branches for the old bootloader ("cm10.1", following CM) and new bootloader ("cm10.1-newbl").
This will hopefully make it easier for devs to support both bootloaders.
Again, pull requests are always welcome.
Please don't discuss gapps related bugs (keyboard closing, gtalk video not working etc.) in here, there's a dedicated thread about non-neon gapps.

1st update:
I digged into the Wifi Hotspot issue.
One reason it doesn't work seems to be that cyanogen reverted a P990 specific patch in the netd package for merging Android 4.2 sources.
Link: https://github.com/CyanogenMod/android_system_netd/commit/d2fe72845348bb1c9e67d2cf3c648e68a93be05f
We need to bring that back. But the structure of the SoftapController.cpp changed substantially, I (or whoever beats me to it) need to look into it closer to determine who to apply the custom patch with the new format.
Additionally I just committed the bootanimation fix:
https://github.com/p990-dev/android...mmit/e298d5c00afb1eb057f1599dd8a71ba677c3c6ca

HI tonyp, another bug is "in-call" mic muting. We can't mute the mic when in call, even when muted, the voice goes through. It's present in CM 10 as well as 10.1. Secondly, I found a temporary solution for Bluetooth A2DP accelerated streaming, keep your Bluetooth turned on and reboot the phone. When the phone connect immediately after booting, the streaming works normal. However when you disconnect subsequently and try to connect again, the music streaming will be accelerated again

About bluetooth, just found a similar issue reported on the HTC One X forums (http://forum.xda-developers.com/showpost.php?p=38647415&postcount=11481). Similar as in same log output, probably not in the result. But both our logs and his log show that there's a buffer overload that after a few starts exploding (our log follows)
Code:
...
03-07 19:54:21.230 W/bt-btif ( 834): btif_media_aa_prep_2_send congestion buf count 25
03-07 19:54:21.230 W/bt-btif ( 834): btif_media_aa_prep_2_send congestion buf count 24
03-07 19:54:21.230 E/GKI_LINUX( 834): ##### ERROR : timer_thread: tick delayed > 5 slots (-547249208,-50000000) -- cpu overload ? #####
03-07 19:54:21.230 E/GKI_LINUX( 834): ##### ERROR : timer_thread: tick delayed > 5 slots (-538364208,-50000000) -- cpu overload ? #####
03-07 19:54:21.230 E/GKI_LINUX( 834): ##### ERROR : timer_thread: tick delayed > 5 slots (-529468208,-50000000) -- cpu overload ? #####
03-07 19:54:21.230 W/bt-btif ( 834): btif_media_aa_prep_2_send congestion buf count 25
03-07 19:54:21.230 E/GKI_LINUX( 834): ##### ERROR : timer_thread: tick delayed > 5 slots (-520578208,-50000000) -- cpu overload ? #####
03-07 19:54:21.230 W/bt-btif ( 834): btif_media_aa_prep_2_send congestion buf count 24
03-07 19:54:21.240 E/GKI_LINUX( 834): ##### ERROR : timer_thread: tick delayed > 5 slots (-511690208,-50000000) -- cpu overload ? #####
03-07 19:54:21.240 W/bt-btif ( 834): btif_media_aa_prep_2_send congestion buf count 25
03-07 19:54:21.240 E/GKI_LINUX( 834): ##### ERROR : timer_thread: tick delayed > 5 slots (-502803208,-50000000) -- cpu overload ? #####
03-07 19:54:21.240 W/bt-btif ( 834): btif_media_aa_prep_2_send congestion buf count 24
...
Of course this leads to faster / slower output (in any case inconsistent). Now, the interesting report from that guy on the One X forum is that bt works fine when wifi is off, and doesn't when it's in COEX mode. Anyone that is able to reproduce the problem, please, can you log an a2dp streaming session with wifi on and one with wifi off ? I need to see if there are different outputs and i'm not on 10.1 at the moment. Probably later today or in the weekend i'll setup dual boot so i can test first hand.

Pengus, I cam confirm that BT without wifi works the same way. I pair my phone for music streaming in my car and it's the same accelerated streaming.

tonyp said:
As the other CM10.1 threads usually are overrun by users let's try to make use of the new section and create a new bug thread in here.
[*]HDMI orientation broken.
The problem is: the GB libnvdispmgr_d.so blob contained a method NvDispMgrAutoOrientation() to change the orientation.
The ICS binary doesn't have that anymore, and pengus and I couldn't figure out yet how to achive the rotation.
(and no, using the old blob won't work).[/LIST]
Please don't discuss gapps related bugs (keyboard closing, gtalk video not working etc.) in here, that'll happen in a dedicated thread.
Click to expand...
Click to collapse
About the hdmi this is also an issue on the P920 what i think lg did here was set the natural orientation in surface flinger to landscape 90 then countered it to 0 when using auto sensor while on cm10+ its @ 0 the hdmi output only reads the default orientation

defcomg said:
About the hdmi this is also an issue on the P920 what i think lg did here was set the natural orientation in surface flinger to landscape 90 then countered it to 0 when using auto sensor while on cm10+ its @ 0 the hdmi output only reads the default orientation
Click to expand...
Click to collapse
Something like that. I managed to have portrait hdmi work correctly changing only a bit of rom code in surface flinger, but the rotation to full landscape mode is achievable only using private methods from the blobs or, as i'm attempting to do, by hijacking the hdmi output and sensor orientation directly in the kernel at the framebuffer level.

pengus77 said:
Something like that. I managed to have portrait hdmi work correctly changing only a bit of rom code in surface flinger, but the rotation to full landscape mode is achievable only using private methods from the blobs or, as i'm attempting to do, by hijacking the hdmi output and sensor orientation directly in the kernel at the framebuffer level.
Click to expand...
Click to collapse
from my understanding its surface flinger -> hwc -> framebuffer
in my case the current output is 648x1080 if i were to make changes @ kernel level would it not result in 1080x648 not 1920x1080? do you guys use ida pro to check lib exports?

defcomg said:
from my understanding its surface flinger -> hwc -> framebuffer
in my case the current output is 648x1080 if i were to make changes @ kernel level would it not result in 1080x648 not 1920x1080? do you guys use ida pro to check lib exports?
Click to expand...
Click to collapse
I'm waiting to get my hands on the hex-ray arm decompiler... soon
Anyway this is the base init of the hdmi fb in kernel world
Code:
static struct tegra_fb_data star_hdmi_fb_data = {
#ifdef CONFIG_MACH_STAR
.win = 0,
.xres = 1366,
.yres = 768,
.bits_per_pixel = 16,
#else
.win = 0,
.xres = 800,
.yres = 480,
.bits_per_pixel = 32,
#endif
.flags = TEGRA_FB_FLIP_ON_PROBE,
};
In fact on boot it's correctly set, then it rotates when surfaceflibger/hwc takes control and never get back to the right mode.
Moreover in the drivers/video/tegra/dc/hdmi.c source file we can see that both 720p and 1080p resolutions are supported by the driver, together with 480p and 576p modes.
As soon as i'll get hex-rays i'll decompile the ics surfaceflinger lib and try to see what externals it calls for panel setup / rotation. I guess it'll happen somewhere next week.

Guys please do not push this thread without reason - so no "thank you" posts, no "good luck" posts and stuff like that.
Each post in here should have a valid reason (read: should be development related).
Read the instructions of the developer discussion section first.
Thank you

pengus77 said:
I'm waiting to get my hands on the hex-ray arm decompiler... soon
Anyway this is the base init of the hdmi fb in kernel world
Code:
static struct tegra_fb_data star_hdmi_fb_data = {
#ifdef CONFIG_MACH_STAR
.win = 0,
.xres = 1366,
.yres = 768,
.bits_per_pixel = 16,
#else
.win = 0,
.xres = 800,
.yres = 480,
.bits_per_pixel = 32,
#endif
.flags = TEGRA_FB_FLIP_ON_PROBE,
};
In fact on boot it's correctly set, then it rotates when surfaceflibger/hwc takes control and never get back to the right mode.
Moreover in the drivers/video/tegra/dc/hdmi.c source file we can see that both 720p and 1080p resolutions are supported by the driver, together with 480p and 576p modes.
As soon as i'll get hex-rays i'll decompile the ics surfaceflinger lib and try to see what externals it calls for panel setup / rotation. I guess it'll happen somewhere next week.
Click to expand...
Click to collapse
Further investigation into surfaceFlinger from ics from 2x + p920
Shows ics had this
Code:
.text:00021880 loc_21880 ; CODE XREF: android::SurfaceFlinger::setOrientation(int,int,uint)+24j
.text:00021880 MOVS R1, #1
.text:00021882 STRB.W R7, [R4,#0x6D]
.text:00021886 STRB.W R5, [R4,#0x6C]
.text:0002188A MOV R0, R4
.text:0002188C BL _ZN7android14SurfaceFlinger19setTransactionFlagsEj ; android::SurfaceFlinger::setTransactionFlags(uint)
.text:00021890 ADD.W R0, R4, #0x74 ; cond
.text:00021894 MOV R1, R6 ; mutex
.text:00021896 BLX pthread_cond_wait
.text:0002189A
.text:0002189A loc_2189A ; CODE XREF: android::SurfaceFlinger::setOrientation(int,int,uint)+2Aj
.text:0002189A ; android::SurfaceFlinger::setOrientation(int,int,uint)+64j
.text:0002189A MOV R0, R6 ; mutex
.text:0002189C BLX pthread_mutex_unlock
.text:000218A0
.text:000218A0 loc_218A0 ; CODE XREF: android::SurfaceFlinger::setOrientation(int,int,uint)+12j
.text:000218A0 MOV R0, R5
.text:000218A2 POP.W {R4-R8,PC}
.text:000218A6 ; ---------------------------------------------------------------------------
.text:000218A6
.text:000218A6 loc_218A6 ; CODE XREF: android::SurfaceFlinger::setOrientation(int,int,uint)+Cj
.text:000218A6 ADD.W R6, R0, #0x54
.text:000218AA MOV R0, R6 ; mutex
.text:000218AC BLX pthread_mutex_lock
.text:000218B0 LDRB.W R0, [R4,#0x6C]
.text:000218B4 CMP R0, R5
.text:000218B6 BNE loc_21868
.text:000218B8 B loc_2189A
.text:000218B8 ; End of function android::SurfaceFlinger::setOrientation(int,int,uint)
setOrientation(int,int,uint)
public static native void setOrientation(int display, int orientation, int flags);
think they excluded the method for hdmi from being called from the framework but just ran it from with in the lib
all they would have needed was the orientation value coming from display 0x0 and sent it to display 0x1 ie hdmi
jellybean is using nativeSetDisplayOrientation(IIII)V with the addition of parameter "externalRotation"
by the way getExternalRotation in Display.java is set to 0x0 i don't if CM10 CM10.1 etc knows what todo with "externalRotation" on our devices

Could someone on the newbl who has problems with bluetooth fast-forwarding-sound please try this build:
http://tonyp.hopto.org/temp/cm-10.1-20130311-UNOFFICIAL-p990.zip
My headset doesn't have any problems whatsoever - neither with official CM sources nor with this build, so I need to wait for testers.
Attach a kernel log + logcat as well please.
Oh and of course one of the most annoying bugs:
After unlocking the brightness often gets reset to a way too low value.
Logcat and kernel log don't show any error.
arcee already tried to fix it some time ago (see here) but this didn't fix it fully.
I guess we can workaround it in here:
https://github.com/CyanogenMod/lge-kernel-star/blob/cm-10.1/drivers/video/backlight/aat2870.c

tonyp said:
Could someone on the newbl who has problems with bluetooth fast-forwarding-sound please try this build:
http://tonyp.hopto.org/temp/cm-10.1-20130311-UNOFFICIAL-p990.zip
My headset doesn't have any problems whatsoever - neither with official CM sources nor with this build, so I need to wait for testers.
Attach a kernel log + logcat as well please.
Click to expand...
Click to collapse
Got this bug immideatly with this rom.
dmesg: http://pastebin.com/F0rTb6fR
logcat: http://pastebin.com/08h2bJBW
BT headset: Jabra BT3030

Here is mine. Hope it help.

Does the provided logs help a bit?
Are they sufficient or do you need more?

chp2 said:
Does the provided logs help a bit?
Are they sufficient or do you need more?
Click to expand...
Click to collapse
I finally compiled and flashed a clean 10.1 on my phone. I'm currently working on fixing both bluetooth media and the low I/O. What i found out so far:
- I/O is perfectly fine on ext4 filesystems (system / data / cache) but slow to a crawl on the sdcards (internal and external both). This is most probably a rom-related problem because testing the speed from a shell results in perfectly fine speeds. I'm looking into a fix.
- Bluetooth media is a mess. We're not the only ones facing this problem and it's not related to CM. I've found on google references to the same error on both CM and AOSP. I'm starting to think this one will be messy to fix and i'm following closely the AOSP git activity related to bt and audio.

pengus77 said:
I finally compiled and flashed a clean 10.1 on my phone. I'm currently working on fixing both bluetooth media and the low I/O.....
Click to expand...
Click to collapse
Yeepeee....
Pingus, I have no doubt you'll find the bugs.
(you're the best hehe)
Question : is it possible to use JB 4.1.2 BT subroutines here?

chp2 said:
Yeepeee....
Pingus, I have no doubt you'll find the bugs.
(you're the best hehe)
Question : is it possible to use JB 4.1.2 BT subroutines here?
Click to expand...
Click to collapse
Google changed from bluez to bluedroid in Android 4.2. It would be possible to revert that but it would be extremely messy and is only the last resort.
Sent from my LG-P990 using xda app-developers app

tonyp said:
Google changed from bluez to bluedroid in Android 4.2. It would be possible to revert that but it would be extremely messy and is only the last resort.
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
I understand that you don't want to revert bluedroid to Bluez but I found this when searching on Google where someone has already tried to do so. I'm not a dev so don't know if it was successful.

darkcastleking said:
I understand that you don't want to revert bluedroid to Bluez but I found this when searching on Google where someone has already tried to do so. I'm not a dev so don't know if it was successful.
Click to expand...
Click to collapse
Thank you very much for this, I will check out these instructions on Monday/Tuesday and do another testbuild!
Edit: Oh no, had a quick look, as you can see in the activity stream he deleted a couple repos in january which are linked in the manifest.
Additionally I'll try to revert the Wifi Hotspot changes. It would be better to write a new Interface for the Wifi Hotspot, but I don't really know how to do so.
Both approaches can't be submitted to Gerrit unfortunately, but as long as it works it would be nice.
Hopefully arcee will gain interest into the 2x again some day - I'm pretty sure he can easily fix that stuff, as he knows the Android Source and overall background really well.

[Dev] 1.32.617.30 Dev Edition Rom for Tmobile Wifi Calling

As we all know, the dev edition is the first to receive OTAs, but the thing about the dev edition is that it doesnt have Tmobile wifi calling enabled, and VoLTE
I have managed to get VoLTE to work though so far, but i am stumped in getting Wifi calling to work
i am almost close to getting wifi calling work on 1.32.617.30 but it fails when I try to make a call using wifi only. Can someone check this logcat out and let me know what could be the issue?
any suggestion would be appreciated
Code:
04-10 13:55:24.348 W/BroadcastQueue(1084): Permission Denial: broadcasting Intent { act=com.htc.wfcservice.intent.action.WifiCallStateChanged flg=0x10 (has extras) } from null (pid=-1, uid=-1) requires com.htc.permission.APP_DEFAULT due to registered receiver BroadcastFilter{f1c166c u0 ReceiverList{172da31f 2224 com.android.phone/1001/u0 remote:399d76be}}
04-10 13:55:24.348 D/WFCSwitchPreference(2224): stickyIntent = Intent { act=com.htc.wfcservice.intent.action.WifiCallStateChanged flg=0x10 (has extras) }
04-10 13:55:24.348 D/WFCSwitchPreference(2224): onReceive: com.htc.wfcservice.intent.action.WifiCallStateChanged
04-10 13:55:24.618 D/HtcThemeUtils(22240): Unregister [email protected] for type 0
04-10 13:55:24.618 D/HtcThemeUtils(22240): Unregister [email protected] for type 1
04-10 13:59:41.380 I/ActivityManager(1084): Process com.htc.wfcwificall (pid 22240) has died
04-10 14:01:49.070 E/WifiCallSwitchPreference(2224): new WifiCalling fail com.htc.lib0.HDKLib0Util$HDKException: IPStateListener4Setting or IPManager class not found
04-10 14:01:49.070 E/WifiCallSwitchPreference(2224): mWFC is null

flex360 said:
As we all know, the dev edition is the first to receive OTAs, but the thing about the dev edition is that it doesnt have Tmobile wifi calling enabled, and VoLTE
I have managed to get VoLTE to work though so far, but i am stumped in getting Wifi calling to work
i am almost close to getting wifi calling work on 1.32.617.30 but it fails when I try to make a call using wifi only. Can someone check this logcat out and let me know what could be the issue?
any suggestion would be appreciated
Code:
04-10 13:55:24.348 W/BroadcastQueue(1084): Permission Denial: broadcasting Intent { act=com.htc.wfcservice.intent.action.WifiCallStateChanged flg=0x10 (has extras) } from null (pid=-1, uid=-1) requires com.htc.permission.APP_DEFAULT due to registered receiver BroadcastFilter{f1c166c u0 ReceiverList{172da31f 2224 com.android.phone/1001/u0 remote:399d76be}}
04-10 13:55:24.348 D/WFCSwitchPreference(2224): stickyIntent = Intent { act=com.htc.wfcservice.intent.action.WifiCallStateChanged flg=0x10 (has extras) }
04-10 13:55:24.348 D/WFCSwitchPreference(2224): onReceive: com.htc.wfcservice.intent.action.WifiCallStateChanged
04-10 13:55:24.618 D/HtcThemeUtils(22240): Unregister [email protected] for type 0
04-10 13:55:24.618 D/HtcThemeUtils(22240): Unregister [email protected] for type 1
04-10 13:59:41.380 I/ActivityManager(1084): Process com.htc.wfcwificall (pid 22240) has died
04-10 14:01:49.070 E/WifiCallSwitchPreference(2224): new WifiCalling fail com.htc.lib0.HDKLib0Util$HDKException: IPStateListener4Setting or IPManager class not found
04-10 14:01:49.070 E/WifiCallSwitchPreference(2224): mWFC is null
Click to expand...
Click to collapse
Hi
Would you show me where to download the DEV Ed ROM for the Tmo HTC One M9 ?
Thanks

h4ng0ver said:
Hi
Would you show me where to download the DEV Ed ROM for the Tmo HTC One M9 ?
Thanks
Click to expand...
Click to collapse
He's clearly asking for help with something before releasing it.
Sent From My HTC One (M8)

h4ng0ver said:
Hi
Would you show me where to download the DEV Ed ROM for the Tmo HTC One M9 ?
Thanks
Click to expand...
Click to collapse
I'm making one. I didn't download the rom from anywhere. I have access to the dev edition ruu

flex360 said:
I'm making one. I didn't download the rom from anywhere. I have access to the dev edition ruu
Click to expand...
Click to collapse
Great. I'll be waiting for your ROM.
Thanks for replying

flex360 said:
As we all know, the dev edition is the first to receive OTAs, but the thing about the dev edition is that it doesnt have Tmobile wifi calling enabled, and VoLTE
I have managed to get VoLTE to work though so far, but i am stumped in getting Wifi calling to work
i am almost close to getting wifi calling work on 1.32.617.30 but it fails when I try to make a call using wifi only. Can someone check this logcat out and let me know what could be the issue?
any suggestion would be appreciated
Code:
04-10 13:55:24.348 W/BroadcastQueue(1084): Permission Denial: broadcasting Intent { act=com.htc.wfcservice.intent.action.WifiCallStateChanged flg=0x10 (has extras) } from null (pid=-1, uid=-1) requires com.htc.permission.APP_DEFAULT due to registered receiver BroadcastFilter{f1c166c u0 ReceiverList{172da31f 2224 com.android.phone/1001/u0 remote:399d76be}}
04-10 13:55:24.348 D/WFCSwitchPreference(2224): stickyIntent = Intent { act=com.htc.wfcservice.intent.action.WifiCallStateChanged flg=0x10 (has extras) }
04-10 13:55:24.348 D/WFCSwitchPreference(2224): onReceive: com.htc.wfcservice.intent.action.WifiCallStateChanged
04-10 13:55:24.618 D/HtcThemeUtils(22240): Unregister [email protected] for type 0
04-10 13:55:24.618 D/HtcThemeUtils(22240): Unregister [email protected] for type 1
04-10 13:59:41.380 I/ActivityManager(1084): Process com.htc.wfcwificall (pid 22240) has died
04-10 14:01:49.070 E/WifiCallSwitchPreference(2224): new WifiCalling fail com.htc.lib0.HDKLib0Util$HDKException: IPStateListener4Setting or IPManager class not found
04-10 14:01:49.070 E/WifiCallSwitchPreference(2224): mWFC is null
Click to expand...
Click to collapse
Can ya get me a bit more of the logcat? Might help if ya had someone post a log of the T-Mobile variant successfully starting a call.
Damn, makes me wish I had this phone. LOL

Flex360 loved your sprint M7 ROM from the past and its good seeing you over at the tmobile side of things but porting wifi calling will prove to be impossible. I believe Its been tried numerous times by various developers but I actually never seen it implemented because from what I heard its embedded into the kernel.

shook187 said:
Flex360 loved your sprint M7 ROM from the past and its good seeing you over at the tmobile side of things but porting wifi calling will prove to be impossible. I believe Its been tried numerous times by various developers but I actually never seen it implemented because from what I heard its embedded into the kernel.
Click to expand...
Click to collapse
Im actually making good developments actually
I got the phone to actually detect the apks and libs and all
i think its possible

I can say it's definitely possible. If anyone with logcat skills can check this out. Would be awesome.
http://pastebin.com/Rb257Sne

flex360 said:
I can say it's definitely possible. If anyone with logcat skills can check this out. Would be awesome.
http://pastebin.com/Rb257Sne
View attachment 3260158View attachment 3260159
Click to expand...
Click to collapse
the developers of insertcoin and viperrom should be able to help, their roms usually have Wi-Fi calling using non tmobile ruus

Any status on this, thanks

flex360 said:
Im actually making good developments actually
I got the phone to actually detect the apks and libs and all
i think its possible
Click to expand...
Click to collapse
It's definitely possible. It's working on ViperOneM9 rom. I hope that you can get it working soon, so I can try it out. I like the idea of using the Developer Edition.

The development for these is dead?

hackmania said:
The development for these is dead?
Click to expand...
Click to collapse
No, this was just a dead thread. T-mobile Wi-Fi calling is integrated in leedroid and viper so far. Maybe others?

Teo032 said:
No, this was just a dead thread. T-mobile Wi-Fi calling is integrated in leedroid and viper so far. Maybe others?
Click to expand...
Click to collapse
+1 what others if any.
Sent from my LG-H811 using Tapatalk

aaronrw said:
+1 what others if any.
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
Sorry haven't really been keeping up with the other ROMs. You should do a quick search in the main M9 forum http://forum.xda-developers.com/one-m9/development
There's also this thread: http://forum.xda-developers.com/one-m9/development/t-mobile-wifi-calling-fix-intl-roms-t3109410
although it hasn't been updated lately, but I'm sure someone can give you a better answer.
A lot of ROMs moved onto the new international base and opt out of including T-mobile's WIFI calling because T-mobile's base has not been updated yet. However, I know leedroid is still keeping the old T-mobile base if selected in AROMA setup and flashing his custom Kernel. I am not sure about VIPER anymore since I'm solely running Leedroid for now.
Sorry can't be of more help.

How did you get VoLTE working with T-Mo on the Dev Edition? Thanks.

qus
He's clearly asking for help with something before releasing it.

flex360 said:
As we all know, the dev edition is the first to receive OTAs, but the thing about the dev edition is that it doesnt have Tmobile wifi calling enabled, and VoLTE
I have managed to get VoLTE to work though so far, but i am stumped in getting Wifi calling to work
i am almost close to getting wifi calling work on 1.32.617.30 but it fails when I try to make a call using wifi only. Can someone check this logcat out and let me know what could be the issue?
any suggestion would be appreciated
Code:
04-10 13:55:24.348 W/BroadcastQueue(1084): Permission Denial: broadcasting Intent { act=com.htc.wfcservice.intent.action.WifiCallStateChanged flg=0x10 (has extras) } from null (pid=-1, uid=-1) requires com.htc.permission.APP_DEFAULT due to registered receiver BroadcastFilter{f1c166c u0 ReceiverList{172da31f 2224 com.android.phone/1001/u0 remote:399d76be}}
04-10 13:55:24.348 D/WFCSwitchPreference(2224): stickyIntent = Intent { act=com.htc.wfcservice.intent.action.WifiCallStateChanged flg=0x10 (has extras) }
04-10 13:55:24.348 D/WFCSwitchPreference(2224): onReceive: com.htc.wfcservice.intent.action.WifiCallStateChanged
04-10 13:55:24.618 D/HtcThemeUtils(22240): Unregister [email protected] for type 0
04-10 13:55:24.618 D/HtcThemeUtils(22240): Unregister [email protected] for type 1
04-10 13:59:41.380 I/ActivityManager(1084): Process com.htc.wfcwificall (pid 22240) has died
04-10 14:01:49.070 E/WifiCallSwitchPreference(2224): new WifiCalling fail com.htc.lib0.HDKLib0Util$HDKException: IPStateListener4Setting or IPManager class not found
04-10 14:01:49.070 E/WifiCallSwitchPreference(2224): mWFC is null
Click to expand...
Click to collapse
Is there a thread how you got VoLTE to work?
I am looking at the AT&T M9 but may switch to T-Mobile in the future.
Obviously I would like to the phone to work on both.
The only difference between the AT&T and T-Mobile version are VoLTE (you said this can be made to work), 3G AWS, and Wifi Calling (which I don't care about since I have Google Voice set up to work with SIP).

I guess VoLTE is a no go?