Activity contains TabHost. Robotium test won't start until manual click the second tab at first and the first tab again.

[GoogleCodeExporter]

What steps will reproduce the problem?
My application has TabHost. All tabs are created programmatically.

1. Run Robotium test.
2. Wait for Activity starting.
3. Wait for test starting.
4. See that test is stil not started.
5. Click manually on the second tab in the TabHost. After that click on the 
first tab in the TabHost.
6. See that test was started running.

What is the expected output? What do you see instead?
Test must start at the step 3, without manually clicking.

What version of the product are you using? On what operating system?
I use robotium-solo.3.4.1 and run test on the emulator and device with Android 
2.2.

Please provide any additional information below.

Original issue reported on code.google.com by kostyukh...@gmail.com on 4 Sep 2012 at 5:49

[GoogleCodeExporter]

My email is ymittova@estaxi.ru.

Original comment by kostyukh...@gmail.com on 4 Sep 2012 at 5:50

[GoogleCodeExporter]

Also, I have logged all my startup functions and I have seen, that command 
"solo = new Solo(getInstrumentation(), getActivity());" is most of the time.
My startup method is:
@Override
protected void setUp() throws Exception {
    super.setUp();
    setActivityInitialTouchMode(true);
    solo = new Solo(getInstrumentation(), getActivity());
}

Original comment by kostyukh...@gmail.com on 4 Sep 2012 at 7:57

[GoogleCodeExporter]

Thanks for reporting this. Is it possible for you to send me a sample app that 
exhibits this problem?

Original comment by renasr...@gmail.com on 4 Sep 2012 at 12:35

[GoogleCodeExporter]

Yes, of course. But, we need some time for it. I'll send you it obligatorily.

Original comment by kostyukh...@gmail.com on 5 Sep 2012 at 8:58

[GoogleCodeExporter]

Great. You can just email it to renasreda@gmail.com.

Original comment by renasr...@gmail.com on 5 Sep 2012 at 8:59

[GoogleCodeExporter]

Original comment by renasr...@gmail.com on 11 Sep 2012 at 2:51

[GoogleCodeExporter]

We have created test application, but situation wasn't reproduced.
We assume that the reason of the bug is in our application, but not in 
Robotium. We are starting refactoring and later we will have more information 
about it.
Thanks for your supporting.

Original comment by kostyukh...@gmail.com on 11 Sep 2012 at 4:38

[GoogleCodeExporter]

how to write the code for TabHost? Which method of Solo will be call?
thanks.

Original comment by donglei....@gmail.com on 11 Sep 2012 at 7:44

[GoogleCodeExporter]

How to simulate a click on TabHost or TabSpec?
Thanks.

Original comment by donglei....@gmail.com on 11 Sep 2012 at 8:09

[GoogleCodeExporter]

Thanks for letting me know. Will open up again if issue is reproduced.

Original comment by renasr...@gmail.com on 12 Sep 2012 at 12:53

• Changed state: Invalid

[GoogleCodeExporter]

Hello! I think we have known the reason of this problem. We used for tests 2 
phones: Acer Liquid and Samsung Spica. So, Acer has a custom and specific 
firmware. And Samsung Spica has a firmware, which is not created for this phone 
model.
Two days ago we had bought a new phone - Samsung Galaxy Ace 2. And all tests 
run succesfully on this phone and starts without any manual touch.
So, my suggestion is "the reason of this defect is custom firmware of phone".
Thanks for your support.

Original comment by kostyukh...@gmail.com on 14 Sep 2012 at 7:56