PythonFanPA

For the more traditional (and longer in the tooth like myself) PC gamers, who might also be space sim/combat enthusiasts from years gone by.....anyone else here anxiously awaiting Chris Roberts' Star Citizen?

....and just imagine the potential crossover marketing opportunities!

I'm curious to see what this 'story you'd never believe' turns out to be.

Wow, didn't expect to see that. Or at least, not after all this time.

The round table format ate hairy spiders when drunk. Its towers became bloated after swallowing a mouthful of baby formula. The baby ate his poisoned barbeque chicken ribs without A1 steak sauce. Fix the chair leg before somebody trips and breaks their sister's glass. It peed shards of LTE droppings from bubbly fermented apples. Doctors gouge the helpless when options appear dangerously silly for perpendicular slicing. Around 2pm there was another explosive diarrhea attack that drove Dan to SMS SoftBank, which viciously countered MetroPCS's audacity to compete. Meanwhile, Mexicans discovered sparkly water of Rio which

signal light

Three Mile (Island)

The round table format ate hairy spiders when drunk. Its towers became bloated after swallowing a mouthful of baby formula. The baby ate his poisoned barbeque chicken ribs without A1 steak sauce. Fix the chair leg before somebody trips and breaks their sister's glass. It peed shards of LTE droppings from bubbly fermented apples. Doctors gouge the helpless when options appear dangerously silly for perpendicular slicing. Around 2pm there was another explosive diarrhea attack that drove Dan to SMS SoftBank, which viciously countered MetroPCS's audacity to compete. Meanwhile, Mexicans discovered

Three Bears

strike out

The round table format ate hairy spiders when drunk. Its towers became bloated after swallowing a mouthful of baby formula. The baby ate his poisoned barbeque chicken ribs without A1 steak sauce. Fix the chair leg before somebody trips and breaks their sister's glass. It peed shards of LTE droppings from bubbly fermented apples. Doctors gouge the helpless when options appear dangerously silly for perpendicular slicing. Around 2pm there was another explosive diarrhea attack that drove Dan to SMS SoftBank, which viciously countered MetroPCS's audacity to compete. Meanwhile,

The round table format ate hairy spiders when drunk. Its towers became bloated after swallowing a mouthful of baby formula. The baby ate his poisoned barbeque chicken ribs without A1 steak sauce. Fix the chair leg before somebody trips and breaks their sister's glass. It peed shards of LTE droppings from bubbly fermented apples. Doctors gouge the helpless when options appear dangerously silly for perpendicular slicing. Around 2pm there was another explosive diarrhea attack that drove Dan to SMS SoftBank, which viciously countered MetroPCS's audacity to

I don't know if it makes a difference, but even when I was on the Epic, getting QPST to recognize the phone could be kind of qwirky...that's why I'm specifically suggesting leaving it in disable until you have the phone hooked up to the usb cable, and only then toggling it to Enable. With the Epic you kind of had to do the same thing with the UART modem setting as I recall in order to nudge Windows to load the right driver.

And here's the link for PRL 56009: http://forum.xda-developers.com/showpost.php?p=33653549&postcount=322

Just to be sure, you should be using v2.7 build 378, the latest version of the drivers you need installed is the file "MotorolaDeviceManager_2.3.4", and one other thing you *might* be missing in order to get the device/port to be recognized properly, after you hook up the phone to your usb cable that's plugged into your Macbook, you have to go into the diagnostic menu and set it to enable (to do so, you input ##3424# in the dialer, then press the menu button in the upper righthand corner, then Edit, then change the dropdown from Disable to Enable). At least on a PC using Windows, once you Enable that, Windows will load up the proper driver that will work with QPST. You shouldn't launch QPST until that step has been completed. Also, you should probably change back to Disable in the Diag menu once you're done.

That's for the OG Photon, not the Q. And the Q is different anyway, it requires a later version of QPST in order to work properly (and even then there's at least one issue where the results don't 'appear' flawless even though it still works).

Tomas, I can help you learn how to change to a different PRL on the Q (though side note nod to Robert given his last post---with the assistance of a PC, not purely via the device itself, that I don't know even if it can be done on this device, much less how). The info, as digiblur said, can be found on the XDA forum for the Q, but I'd be happy to write it up as simply as possible and PM it to you if you'd like as well. And also, the newest of the 56XXX line is now 56009. Addendum: on further review, if you only have a Macbook and no access to a PC, then I probably can't help you there unfortunately, unless you have Windows emulation or availability via something like Bootcamp or the like.

I'm back up in PA this weekend, just got in a few minutes ago, and had the Photon Q in LTE-only mode now that I know how to switch to that, and Sensorly running in map mode, from about I-81 mile marker 230 south of Harrisonburg VA all the way to SR283 just east of Harrisburg PA. New areas I found which were previously unmentioned and/or unmapped: (1.) I was able to reaffirm the pocket of LTE north of the already-mapped area of Harrisonburg that I found last time but Sensorly for whatever reason didn't upload into the database properly. Looking at the Sensorly map online right now, while it wasn't yet showing up on my phone, its now showing where I mapped earlier tonight extended up just past exit 264. (2.) Looks like I was also able to get in some more fill-in mapwise from near Edinburg just north of exit 279 up to the Strasburg area which was the southermost consistent point that was previously mapped after Harrisonburg. (3.) As of this posting it doesn't look like the map is updated yet from this point forward, but this time when I transitioned from Maryland into PA, I held onto LTE and stayed solid without any complete disruption all the way to immediately before exit 20. Right now (again, as I type this), Sensorly only shows 3 pockets of LTE at the state line, MM10-12ish, and up around Chambersburg, but I was able to stay with and hopefully map LTE solid all the way through and between those 3 points. (4.) I finally was able to pick up some LTE after hopping on I-76/PA Turnpike this time around. Got a good strong signal from roughly about MM231 to just past the I-83 (Harrisburg/York) gate/offramp. I also picked it up again immediately upon reaching the bridge over the Susquehanna, but it only lasted maybe a half mile at best after getting through the toll gate and onto 283 (and also dropped completely while going through the toll gate I should add). Really hoping those last 2 end up showing up on the map properly as well, but i'm particularly happy I finally got that stubborn patch north of Harrisonburg mapped, that'd been irking me because I knew it was there, but since I'm not exactly local, I couldn't easily just drive back out and try and redo it.

Big Ten

Imageshack is another possibility as well.

high hopes

horse jockey

I finally did the update tonight, had to remove the toggles mod and reflash stock recovery first but it went off without a hitch. Just in time for my trip back up to PA this weekend.

tractor trailer