This is the support thread for the Android version of PokerCruncher, which is an advanced hand ranges and flop odds/texture analysis odds calculator.

Just purchased and beginning to learn. I'm trying to assign a % range. My steps: select player; press rng button -> opens range grid; select % range; press done button -> closes range grid without loading range to player. Any ideas on what I'm doing wrong?

Thanks for getting the app.

After selecting the % range, tap the "Add" button. This turns the selected (orange) cells to yellow (added), and also updates the range text and range %age at the top of the screen from the initial "<Empty>" and 0%.

Also as a shortcut you can double-tap on a player field to open the range editor.

Love the app. Would love to get your other apps on Android as well, any plans to make these available on 'Droid?

Hi,
Thanks for getting the app and for posting. But I have no plans for more Android apps. It's just the operating economics of the two app stores / markets imo. I think apps just sell more on iOS in general. : )

There is a graphics issue on a Samsung GS3 running JB.
After you run a calculation,the tops of the result numbers are chopped off.....

Thanks for reporting this, you're the first to do so.
I think it's part of life in the Android world ... supporting many phone models, many screen resolutions, and multiple OS variants.

I think for many UI bugs a screenshot would help a lot. Can you please attach one in this thread, or email one to me at support@pokercruncher.com?

A screenshot speaks a thousand words, and would answer questions like:
* Exactly which result numbers are chopped off?, just Equity?, or the small Stats view's stats?
* Maybe the font size is larger than expected on your phone for some reason which is causing the numbers to be chopped off?

Thanks, -RJ

Trying this directly from the phone...
Huh. Can't attach from phone I guess

I got your email and screenshot, thanks. I've attached your screenshot here for reference.

The Equity and Tie stats and the NumSimulations counter are shifted up a little by what looks like the same amount. Doesn't happen on my Samsung Nexus or on most other phones I believe (cause this is the first I've heard of this problem), or in the Android simulator, weird. Give me a few days to change the adjustment and test. The trick is fixing this for your phone and not breaking the alignment on the rest of the phones.

I noticed that the text font on your phone is different than what I've seen on most phones. Have you set a custom font and font size on your phone or done anything out of the ordinary for the text font?

Thanks for your help on this problem. -RJ

Have you set a small default font size on your phone? The font size of the Equity/Tie stats looks very small. If so, try changing to a medium font size.

Regardless, the app shouldn't cut off the text, investigating..

Yep, just set it back to default and works fine. One of the reasons I switched to Andoid was the ability to totally customize, just like my Linux PC. This is one of the catches...
Thanks for the great app and put me down as a buyer of your other apps should you decide to port them!!!!

Great, at least we have a workaround (default size). This will also help with the "Calculate", "+ Player", etc. buttons; the text looks small on these buttons.

You definitely should be able to customize so there's still a bug in the app in the vertical alignment of these text fields. I'll investigate this coming week, but won't be able to really start looking til Tue. Whatever fix I make, I've got to be careful to not break the alignment for the medium/default and large text sizes. I expect to submit a fix this coming week.

Thanks for finding this alignment bug, and for your good words on the app and support.
-RJ

Version 6.1.2 is live now with the fix for this. You can now set the system font size to small or normal or large and all stats should be fully visible and not chopped off.

Do let me know if you still see a problem. I tested on several screen sizes and font sizes but only in the simulator; in the Android world it's hard to test on many different actual phone models.

I also made some other improvements:

* Improved the main Help screen and the hand range Help screens. E.g., added info. on the top x% of hands slider's hand ordering/ranking.

* Increased the default number of Monte Carlo sim trials by a factor of 2, for more accurate stats. The latest smartphones are faster and should be able to handle this.

Thanks for reporting the chopped stats bug. -RJ

Nice. Works well. Thanks RJ!!
Please port the ICM app!!! :-}

Great, thanks for your supportive feedback.

Re. the ICM app (Tournament Cruncher), I've held off on porting more apps to Android for now, due to iOS vs. Android sales business reasons, but will re-visit the decision later this year.

sickkkk

What exactly is the deal to hole cards feature and it's use? And can you please explain the hit/make feature. I did tutorial but fail to see the difference. Thank you great app

Good questions.

1) DealTo=HoleCards:

This isn't nearly as useful as DealTo=Flop or DealTo=Turn. I put it in there just for completeness and full flexibility.

But here's a use case: pre-flop, you pick up JJ UTG at a full table. You then wonder what the chances are that someone will pick up AA/KK/QQ? To calc this in the app: set NumPlayers=10, enter JJ for Player1, set DealTo=HoleCards. Calculate and see your equity (87%). This means 13% of the time someone will pick up AA/KK/QQ (and you then have to figure out how to lose as little as possible with your JJ if you miss your set). Well, not quite 87% exactly because someone can pick up JJ to tie you which is also factored into the equity, but there's just one remaining combo of JJ so that's not much interference. There's a formula out there on the internet for figuring this out for any given pocket pair, but the app doesn't care about formulas and can handle any situation you set up.

2) Hit vs. Make stats:

Usually you want to be in "Hit stats" mode because the "Make stats" mode includes cases where the board helps make the hand, for example when there's a pair on the board and you make TwoPair but really only hit OnePair.

Here's the example in the tutorial:



So JTs *hits* OnePair on the flop about ~27% of the time, hits TwoPair ~2% of the time, etc. Tap the Hit/Make button; the *make* stats are ~40% and ~4% respectively. Comparing the hit vs. make stats can be useful. But usually you want to see the "hit" stats.

Thanks for buying/using the app and sending questions.
And a gentle reminder that app store reviews help the app and small devs a lot. : )

I just purchased PokerCruncher and it looks OK.
However, I just tried a simple calculation and compared it to the same calculation using PokerStove.
2c2s against AhKd came out to 61.1% to 38.9% on PC and 53.04% to 46.96% on PS.
Why is there such a discrepancy?

You have accidently set Deal-To = Turn, instead of = River. Starting clean with a ResetAll is a good practice.

The app has a warning/informational alert when you change Deal-To. This is an advanced feature that PokerStove doesn't have. E.g. Deal-To-Flop gives you many additional stats and lets you do flop texture analysis. I invite you to read the app's tutorial to learn about this feature.

Thanks for buying the app.

Thanks for the quick reply.
That certainly gives a different result (same as PS).
I hadn't touched Deal-To so it is obvious I need to take a close look at the tutorial.

I understand the iOS version of PokerCruncher includes the ability to calculate a chip/icm tournament chop. Is this also part of the Android version?

Hello, no, the iOS version of PokerCruncher doesn't have this feature. ICM/chip-chop, etc. are in a separate app of ours called "Tournament Cruncher". No plans yet to make an Android version.

Thanks for the response. Is it possible with Tournament Cruncher to have a "custom" chop calculation?
i.e., if one player has an advantage/disadvantage in skill, can there be input to reflect that?

Players' skill factors isn't a direct/explicit feature in the app, but it can be approximated. First, save the original scenario. Then, if you want to model that a player has twice the skill of the remaining players, double that player's stack size. Similarly for half/two-thirds/etc. the average skill. Then save the modified scenario as well, and you can go back and forth between the original and modified to compare.

The mapping between skill and the stack size modification probably isn't linear as written above, but linear should be a good approximation. Good question/feature btw.