Jump to content

Keep a Word, Drop a Word #4


S4GRU

Recommended Posts

We have started a new thread for KAW-DAW. The previous thread is now over 5,000 entries and has been closed. 

If you've never played Keep a Word, Drop a Word before, it is really simple. See below...

 

Example Post 1: customer satisfaction

Example Post 2: tough customer

Example Post 3: tough break

Example Post 4: break wind

 

Comprendo? See, it is really simple.

  • For each new post just keep a word from the previous post and drop the other and replace with a new one.
  • Please KEEP your posts to JUST 2 WORDS, but if you are stuck and must to, you can include a "helper" word, like: a, the, an, etc. BUT the next post CANNOT use that "helper" word as the one they keep for the next post.
  • You can however use the same "keep" word as the previous poster if you want to.
  • Otherwise just have fun with it and let's see where it goes? If things get stalled out just start a new line of thought by making a new 2 word saying.

I will kick off the game below...

  • Like 2
Link to comment
Share on other sites

Booty club

 

Sent from my EVO using Tapatalk 4 Beta

 

 

Link to comment
Share on other sites

Booty meat

 

Sent from my EVO using Tapatalk 4 Beta

 

 

Link to comment
Share on other sites

Deer meat

 

Sent from my EVO using Tapatalk 4 Beta

 

 

Link to comment
Share on other sites

Short loaf

 

Sent from my EVO using Tapatalk 4 Beta

 

 

Link to comment
Share on other sites

Sergeant Peppers

 

Sent from my EVO using Tapatalk 4 Beta

 

 

Link to comment
Share on other sites

Drill Sergeant

 

Sent from my EVO using Tapatalk 4 Beta

 

 

Link to comment
Share on other sites

Blood diamond

 

Sent from my EVO using Tapatalk 4 Beta

 

 

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • It is an Android bug that was reportedly fixed in August 2023 but definitely has not been. I have implemented numerous workarounds in SCP to correct the NR bands the app displays. The OS ignores the possibility that many NR-ARFCNs are valid across multiple bands.. it reports the lowest NR band that is valid for the current ARFCN. In your example, channel 432530 can be n1, n65, or n66.. so the OS just (lazily) reports n1.   Awesome, thanks! I will add an n65 override also.
    • Yeah both of those instances were on my AT&T s22 ultra. Seems ro be working as intended today in latest release.
    • Interesting, I saw this too on my AT&T S22 while roaming on US Cellular. I thought it was an Android bug since CellMapper was doing the same thing (didn't get a screenshot of that one). N66 makes more sense than N1. 
    • Thanks, that was good timing, I did see your report as I was buttoning up this latest update and added an override for that.. did it not work?   Ok, was that on AT&T also? Please send a report if you happen to see it again and safely have the opportunity. You can always do the long-press on the fly and then send a later one with an explanation pointing to the earlier one.. your username is attached to the long-press reports, so it's not an issue.
    • I sent a report in earlier, n66 reporting as n1. There should be two different reports, I couldn't find the button the first time so I just long pressed the connection type to send, then I remembered where it was. I put a note about the issue on the 2nd report. Both reports from me are for the same issue. Also, it might have been on a prior release but earlier this week I also saw n66 reported as n65 on the app. I was driving and wasn't able to send a report in for that one. 
  • Recently Browsing

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