I have a fully functioning Android app that works properly in various simulators running 2.2, 4.2.2 and 4.3. However, this is ONLY true when hardware navigation buttons are specified on the device simulator. If I define an AVD with hardware buttons enabled, the app runs fine in full screen with the status bar visible at the top, which I desire. This is the case whether I invoke a skin with hardware controls or not with the AVD.
If I start the AVD without hardware navigation buttons enabled, then in 4.0+ Android versions the "software" navigation buttons (HOME, BACK, etc) are enabled. The app fails to launch and I get a solid gray screen. I am "guessing" this has something to do with usable screen real-estate. Anyone else seen this in your efforts?
ANDROID - Navigation Bar Challenges
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller
Re: ANDROID - Navigation Bar Challenges
Hi jjt,
I think the word around town is the AVD is notoriously ummm.... crap.
Best is to test on a real device.
Not saying the AVD is useless but it does not reflect a real device 100%.
Simon
I think the word around town is the AVD is notoriously ummm.... crap.
Best is to test on a real device.
Not saying the AVD is useless but it does not reflect a real device 100%.
Simon
I used to be a newbie but then I learned how to spell teh correctly and now I'm a noob!
Re: ANDROID - Navigation Bar Challenges
Simon-
Thanks for the reply. I have found the AVD to be "challenging" for sure. However, I generally have been able to get it to work as desired and successfully port my iOS app to the ANDROID platform. My concern is that there is something programmatically wrong that is causing the app to fail if the software navigation buttons are present. I realize the AVDs have limitations, but since it is all I have, I'm looking to see if others have had similar experience.
I wish I could afford to go out there and buy the 6 - 10 most popular ANDROID devices and develop with them directly. However, I don't make any money selling apps and I do it solely for fun by building tools my corporate peers can leverage. So, spending that kind of money does not bode well for spousal relations.
Have you seen this kind of behavior with the AVD and hardware vs. software navigation? ... in particularly where it failed on the AVD, but worked fine on an actual device?
Thanks again for the feedback.
Thanks for the reply. I have found the AVD to be "challenging" for sure. However, I generally have been able to get it to work as desired and successfully port my iOS app to the ANDROID platform. My concern is that there is something programmatically wrong that is causing the app to fail if the software navigation buttons are present. I realize the AVDs have limitations, but since it is all I have, I'm looking to see if others have had similar experience.
I wish I could afford to go out there and buy the 6 - 10 most popular ANDROID devices and develop with them directly. However, I don't make any money selling apps and I do it solely for fun by building tools my corporate peers can leverage. So, spending that kind of money does not bode well for spousal relations.
Have you seen this kind of behavior with the AVD and hardware vs. software navigation? ... in particularly where it failed on the AVD, but worked fine on an actual device?
Thanks again for the feedback.
Re: ANDROID - Navigation Bar Challenges
H jjt,
I have not seen the navigation btns to be a problem but then I haven't tried many variations of the AVD.
I do have an app running on devices with and without hardware buttons and it's working fine.
Simon
I have not seen the navigation btns to be a problem but then I haven't tried many variations of the AVD.
I do have an app running on devices with and without hardware buttons and it's working fine.
Simon
I used to be a newbie but then I learned how to spell teh correctly and now I'm a noob!