Jump to content

Question for Photon Q owners experiencing the Sensorly map-halting issue


PythonFanPA

Recommended Posts

Those of you with P-Q's, I need to ask something, as its been a a possible theory I have on this issue:  are any or all of you, when experiencing the mapping problem with this, also using a bluetooth connection of any kind actively at the same time?


 


The reason I ask is that I did some mapping today in one of the towns in the area I cover with work, and I had the mapping process go 23-24 minutes today without crapping out on me at all (I finally manually stopped it when I had to get back to what I was doing from my lunch break). This was in a work vehicle in which I had no bluetooth connection going on with anything. Comparatively, ever since the JB update, usually the highest I hit was not even 15 minutes (and most of the time 10 or less) before the halt on the mapping process occurred, and every time I've tried to map since the JB update (up until today), I've also been connected to my car's aftermarket Kenwood KDC-X597 receiver via a bluetooth connection for phone and possible streaming connectivity through the phone (though not always with active phone call or streaming in progress when the halt happened, just a live bluetooth connection).


 


Its entirely possible I was just extremely lucky today, but I'm curious to see if anyone can say 100% without a doubt they still had the mapping process halt with bluetooth completely disabled on the phone.


  • Like 2
Link to comment
Share on other sites

 . . .

are any or all of you, when experiencing the mapping problem with this, also using a bluetooth connection of any kind actively at the same time?

 . . .

 

I can't thank you enough! After disabling bluetooth, I had the first perfect mapping trip in months.

 

:D  :tu:

  • Like 1
Link to comment
Share on other sites

Unfortunately, I have to report that the bluetooth connectivity is not the root cause of this.  It may 'speed it up' somehow, but during mapping attempts the past 2 days to/from visiting family for the 4th, I had the mapping process halting problem still happen with no bluetooth enabled at all, and still shows at least a triple-digit reading in the battery usage afterwards.

 

The good news is the Sensorly dev is supposedly going to be adding me as a beta tester, so hopefully I can help get this issue nailed down so it can be fixed.

  • Like 4
Link to comment
Share on other sites

As of today I'm officially on the beta stream of the app.  I'll be making a trip up to PA next Friday and returning on the 28th, so hopefully with 2 650ish mile trips to try mapping on it'll help the dev figure out what's causing this.

  • Like 2
Link to comment
Share on other sites

Happy to report that while I can't say 100% for certain yet this issue is completely solved on the beta stream, progress is being made.  The root cause has definitely been identified;  apparently Motorola phones don't report battery statistics correctly (or at least normally compared to other phones) in Android. The dev had found an undocumented workaround previously which worked up till now, but something in the JB update for this phone changed things.  When I sent him log files to review, he discovered that the phone wasn't reporting to the app properly in 10% increments, but rather over a 20 second period it reported 70, then 100, then -14 percent (weird I know).  

 

He put out a new update on the beta stream the next day, and after I had a ~50 minute work road trip to another office that I tested with (and I made a point to have bluetooth on even though I didn't have another device to pair to), the mapping process didn't halt during that frame of time.  My Friday trip 9-10 hour drive to PA will be the true litmus test, but if nothing else, this is definitely progress!  :tu:

  • Like 3
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • Excuse my rookie comments here, but after enabling *#73#, it seems that the rainbow sim V2? requires n70 (I turned it off along with n71 - was hoping to track n66) to be available else it switches to T-Mobile.  So this confirms my suspicion that you need to be close to a site to get on Dish.  Have no idea why they don't just use plmn. To test, I put it into a s21 ultra, rebooted twice, came up on T-Mobile (no n70 on s21).  Tried to manually register on 313340, but it did not connect (tried twice). I am on factory unlocked firmware but used a s22 hack to get *#73# working.  Tried what you were suggesting with a T-Mobile sim partially installed, but that was very unstable with Dish ( I think they had figured that one out).  [edit: and now I see Boost sent me a successful device swap notice which says I can now begin to use my new device.  Sigh.  Will try again later and wait for this message - too impatient.]
    • Hopefully this indicates T-Mobile hasn't completely abandoned mmwave and/or small cells? But then again this is the loop, so take that as you will. Hopefully now that most macro activity is done (besides rural colo/builds), they will start working on small cells.   
    • This has been approved.. https://www.cnet.com/tech/mobile/fcc-approves-t-mobiles-deal-to-purchase-mint-mobile/  
    • In the conference call they had two question on additional spectrum. One was the 800 spectrum. They are not certain what will happen, thus have not really put it into their plans either way (sale or no sale). They do have a reserve level. Nationwide 800Mhz is seen as great for new technologies which I presume is IOT or 5g slices.  T-Mobile did not bite on use of their c-band or DOD.  mmWave rapidly approaching deadlines not mentioned at all. FWA brushes on this as it deals with underutilized spectrum on a sector by sector basis.  They are willing to take more money to allow FWA to be mobile (think RV or camping). Unsure if this represents a higher priority, for example, FWA Mobile in RVs in Walmart parking lots working where mobile phones need all the capacity. In terms of FWA capacity, their offload strategy is fiber through joint ventures where T-Mobile does the marketing, sales, and customer support while the fiber company does the network planning and installation.  50%-50% financial split not being consolidated into their books. I think discussion of other spectrum would have diluted the fiber joint venture discussion. They do have a fund which one use is to purchase new spectrum. Sale of the 800Mhz would go into this. It should be noted that they continue to buy 2.5Ghz spectrum from schools etc to replace leases. They will have a conference this fall  to update their overall strategies. Other notes from the call are 75% of the phones on the network are 5g. About 85% of their sites have n41, n25, and n71, 90% 5g.  93% of traffic is on midband.  SA is also adding to their performance advantage, which they figure is still ahead of other carriers by two years. It took two weeks to put the auction 108 spectrum to use at their existing sites. Mention was also made that their site spacing was designed for midrange thus no gaps in n41 coverage, while competitors was designed for lowband thus toggles back and forth for n77 also with its shorter range.  
    • The manual network selection sounds like it isn't always scanning NR, hence Dish not showing up. Your easiest way to force Dish is going to be forcing the phone into NR-only mode (*#*#4636#*#* menu?), since rainbow sims don't support SA on T-Mobile.
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...