jefbal99

51 minutes ago, mikejeep said:

New beta just uploaded, should be available within the hour! Hopefully will fix the custom trigger crashes, pre-Oreo crashes, missing WCDMA/GSM data, and missing Android Q data.. please pass along any improvements you notice!

-Mike

Woot, have data!!!

6 hours ago, dkyeager said:

starred.  Now up to 6.  Need a lot more people to star it since Google is numbers driven on what it chooses to fix.

2 hours ago, mikejeep said:

 

Q Beta 2 might be reporting enough info for me to work with. I have to implement workarounds in to ignore the some of the invalid information that it is reporting and see what's left. Another complication is that Q is identifying itself as API 28, which is the same as Pie. I'm working on it..

-Mike

 

Up to 7 now and its been assigned in the tracker

40 minutes ago, mikejeep said:

Blah.. thanks. I starred your new issue report and added a comment. Did your original report on the issue tracker from a few weeks ago disappear? I haven't seen any diagnostic or crash reports from you yet today.

-Mike

Sent it about an hour ago. I'll send another right now

Please go and Star 

https://issuetracker.google.com/issues/130132884

4 minutes ago, mikejeep said:

I believe I have resolved the force closes on pre-Oreo devices as well as the force closes with the custom LTE alert. Need to do a bit more testing but I should be all set with additional reports about those, thank you to all who have sent crash reports--it is very difficult to fix anything without that data, I appreciate it!

Has anyone (@jefbal99?) tried using SCP with Android Q Beta 2 yet? Curious to see if anything has improved yet. If you can get it to run at all, please send me a diagnostic report so I can see how it's doing.

-Mike

Same errors still, not sure if Google actually fixed the issue.  Sending you a new log

16 hours ago, jefbal99 said:

It's on reddit now.  Please comment and upvote https://www.reddit.com/r/android_beta/comments/b2n6z5/connection_data_not_being_reported_from_q/

Google responded on reddit, looks like it will be addressed

12 hours ago, mikejeep said:

After looking at a handful of diagnostic and crash reports that I have received from Android Q Preview users, I can see that the connection data being reported by the OS is either missing or invalid on all devices so far. It's either broken or Android is taking a completely different approach and has not publicly shared that yet. Hopefully it's just broken, and they will resolve it in the next release.

Q users, please use whatever reporting channels are in place to report Preview bugs to inform them of this. You can mention that onSignalStrengthsChanged() is including header text with every value instead of just the raw data, and CellInfoLte.getCellIdentity() and related routines appear to be reporting no data.

-Mike

Its on reddit now, please comment and upvote

https://www.reddit.com/r/android_beta/comments/b2n6z5/connection_data_not_being_reported_from_q/

12 hours ago, mikejeep said:

After looking at a handful of diagnostic and crash reports that I have received from Android Q Preview users, I can see that the connection data being reported by the OS is either missing or invalid on all devices so far. It's either broken or Android is taking a completely different approach and has not publicly shared that yet. Hopefully it's just broken, and they will resolve it in the next release.

Q users, please use whatever reporting channels are in place to report Preview bugs to inform them of this. You can mention that onSignalStrengthsChanged() is including header text with every value instead of just the raw data, and CellInfoLte.getCellIdentity() and related routines appear to be reporting no data.

-Mike

It's on reddit now.  Please comment and upvote https://www.reddit.com/r/android_beta/comments/b2n6z5/connection_data_not_being_reported_from_q/

1 minute ago, mikejeep said:

 

I have spent a TON of time on it because I'm overhauling Alerts for Android 8+ users. They were broken and I don't want to push another update out without a fix. It's a lot of work but it's getting there.

 

Send me a diagnostic report from the Q Preview so I can get a peek at what's broken. Most early Preview builds have caused issues that were eventually resolved before the stable launch.

 

And thanks for the bday wishes!!

 

-Mike

 

I sent one in last night, let me know if you need another

Hoping for a new beta soon, just updated to the Android Q beta and SCP isn't displaying any data

Not sure what to do, my Pixel 2 XL has decided that it no longer likes my MB.  It just won't see the MB.  I'm bouncing between t-mobile roaming that screws up my clock, to over subscribed B26, to weak B41 that barely works, to occasionally B25 that works.  However, B25 gets handed off very quickly to one of the other bands.

Randomly on Monday my phone latched on to the MB and stayed there until I ran into town, when I got home, it wouldn't see it.  It seems that the longer I stay in the house, eventually my phone will see the MB, but it's very inconsistent.

I worked with Customer Care, however, they told me to take my phone to a Sprint store for diagnostics.

My MB appears to be fine as my HotSpot connects to it just fine and never leaves.  My neighbors and family Sprint devices hook to it just fine.  I've done all the standard system updates, PRL, Profile, etc.

Used to be that as soon as I got into my garage I was on the MB and my phone never went to the Macro until I was driving away.

Any suggestions, thoughts, ideas?

New beta out?

Yes, I'm seeing the GMT timezone issue as well when roaming on TMobile in West Michigan too

On 11/16/2018 at 1:35 AM, Dkoellerwx said:

1x800 is usable at greater distances from the cell site than any other LTE signals. Plenty of reasons why LTE might not be available or reliable. 

 

Plus they seem to be adjusting roaming levels, allowing it when Sprint LTE signals are just weak, not all together absent. 

My biggest issue currently is that when I roam on the local t-mobile site, it changes my system time to GMT and screws up all kinds of shit

I've seen TMobile roaming around Portland, so its well into West Michigan.  It's not consistent, but its filling gaps

On 10/21/2018 at 8:03 PM, notsrealinc said:

T-Mobile roaming in East Lansing!

Have you guys seen roaming at all too?

 

I haven't seen anything, but I also haven't been actively looking either.  I've got a few spots out by Portland that should be covered by T-Mobile Roaming, but I still just lose service.

9 hours ago, ingenium said:

Googled for "opt out Android beta" and this was the first result https://www.google.com/android/beta

Looks like it should work (I never enrolled in the beta program).

Sent from my Pixel 2 XL using Tapatalk
 

So weird, I did the same searches and ended up in different places.  Thanks for the assist and I now have the Oct update

9 hours ago, ingenium said:

Only if you revert to stable. Right now there is no beta, and you're on the stable channel already. You have to reset only because downgrades aren't supported.

Sent from my Pixel 2 XL using Tapatalk
 

so going to android.com/beta takes me to https://developer.android.com/about/versions/pie/ and for the life of me I can't find an opt out option.

On 10/8/2018 at 1:33 PM, though said:

Get on the 'normal' channel and you should be able to get it on day 1 from here on out...

I thought opting out of the beta would require a device reset?  Is that not true any longer?

7 minutes ago, though said:

You never opted in for the beta Pie releases?

i never opt'd out

58 minutes ago, ingenium said:

Did you ever opt in for the beta of pie? If you don't leave the beta then you won't receive the update.

Sent from my Pixel 2 XL using Tapatalk
 

Hmm, I got the Sept security update normally

3 minutes ago, though said:

Go to settings, system, advanced, system update, check for update

oh i have multiple times, just haven't gotten to me in the availability yet.

On 9/30/2018 at 10:12 PM, notsrealinc said:

Freshly installed Airspan small cell on Chicago Ave and W Saginaw St:

I saw BWL install power on the 24th. Has yet to be powered on. It seems to be backhualed by Ethernet (not relay). Ideas as to the ISP (possibly Lightspeed)?

Location:

https://www.google.com/maps/place/700+Chicago+Ave,+Lansing,+MI+48915/@42.7409101,-84.5699107,17z/data=!4m5!3m4!1s0x8822ea875eebe707:0x7d7b14ec78f48ad4!8m2!3d42.741052!4d-84.5643317

I've seen a few SC connections pop up in SCP in the last two weeks, hope to see more density as it is needed!

I got the carrier services update a few days ago, but still living on the Sept Security patch.  Haven't gotten the Oct patch yet

How often are you uploading where you need CA UL?