Jump to content

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

PythonFanPA

By PythonFanPA
in Motorola

 Share

Recommended Posts

PythonFanPA Member Level: LTE Advanced

PythonFanPA

Posted
Posted

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
Hugo Member Level: 3G EVDO

Hugo

Posted
Posted

 . . .

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
PythonFanPA Member Level: LTE Advanced

PythonFanPA

Posted
  • Author
Posted

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
PythonFanPA Member Level: LTE Advanced

PythonFanPA

Posted
  • Author
Posted

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
PythonFanPA Member Level: LTE Advanced

PythonFanPA

Posted
  • Author
Posted

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.

×
 Share
Go to topic listing

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • topdownat4
      Keep a Word, Drop a Word #7

      By topdownat4 · Posted

      Fury Gran Coupe (My First Car - What a Boat...)
    • dkyeager
      Dish Network/Boost Mobile cell/5G buildout thread

      By dkyeager · Posted

      Definite usage quirks in hunting down these sites with a rainbow sim in a s24 ultra. Fell into a hole yesterday so sent off to T-Mobile purgatory. Try my various techniques. No Dish. Get within binocular range of former Sprint colocation and can see Dish equipment. Try to manually set network and everybody but no Dish is listed.  Airplane mode, restart, turn on and off sim, still no Dish. Pull upto 200ft from site straight on with antenna.  Still no Dish. Get to manual network hunting again on phone, power off phone for two minutes. Finally see Dish in manual network selection and choose it. Great signal as expected. I still think the 15 minute rule might work but lack patience. (With Sprint years ago, while roaming on AT&T, the phone would check for Sprint about every fifteen minutes. So at highway speed you could get to about the third Sprint site before roaming would end). Using both cellmapper and signalcheck.net maps to hunt down these sites. Cellmapper response is almost immediate these days (was taking weeks many months ago).  Their idea of where a site can be is often many miles apart. Of course not the same dataset. Also different ideas as how to label a site, but sector details can match with enough data (mimo makes this hard with its many sectors). Dish was using county spacing in a flat suburban area, but is now denser in a hilly richer suburban area.  Likely density of customers makes no difference as a poorer urban area with likely more Dish customers still has country spacing of sites.
    • dkyeager
      SignalCheck Beta Crew Forum

      By dkyeager · Posted

      Mike if you need more Dish data, I have been hunting down sites in western Columbus.  So far just n70 and n71 reporting although I CA all three.
    • S4GRU
      Keep a Word, Drop a Word #7

      By S4GRU · Posted

      Nissan Coupe
    • Paynefanbro
      Network Vision/LTE - New York City Market

      By Paynefanbro · Posted

      Good catch! I meant 115932/119932. Edited my original post I've noticed the same thing lately and have just assumed that they're skipping it now because they're finally able to deploy mmWave small cells.

  • Recently Browsing

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