Author Topic: Samsung Galaxy S4 Unity + NGUI Issues?  (Read 4845 times)

FussenKuh

  • Newbie
  • *
  • Thank You
  • -Given: 0
  • -Receive: 0
  • Posts: 6
    • View Profile
Samsung Galaxy S4 Unity + NGUI Issues?
« on: May 23, 2013, 01:18:33 PM »
I apologize for this post being a bit vague. I don't have all the info I'd hope to have in front of me at the moment... but, I figured I'll at least get the ball rolling.

Unity Version: The last 3.5.x build. (I think it's 3.5.7)
NGUI Version: Paid version. Actual version number unknown at the moment (don't have my build environment available to me at the moment). Grabbed the build that would have been available in early March 

After finding NGUI a few months ago, development of the UI in my Android game has been a pleasure. I'm not doing anything very fancy (nothing more than some position/scale tweening, a couple clipped panels, pulldown menus and button pressing). The UI works perfectly on many devices (Galaxy S3, S2, S, Motorola Droid 3, 4, Incredible, Nexus 7 and several other old models).

However, an out-of-town friend just got a Galaxy S4 and attempted to run my game. Unity starts without issue; he can see my Main Menu screen. But, as soon as he attempts to interact with any NGUI element the game will crash back to the Android home screen. He's tried pressing buttons and entering text into the game's sole text input box. Attempting either, ends with the same crash results.

I've sent him an early prototype of a different game that does not use NGUI and it runs on his S4 without issue. i.e. touch inputs for the non-NGUI based game don't crash said game.

Again, I apologize for the lack of any further concrete details at the moment; I'm certainly making many assumptions that something in NGUI (or my incorrect integration of NGUI components) is causing this issue.

My question to the forum community is if anyone has encountered any application crash issues or if anyone knows of any oddities when running on a Galaxy S4 (or any other high resolution Android device). My mind is being pulled toward 'resolution issue' simply because I don't see this issue on any of my non-high resolution devices nor do I see the issue on my Nexus 7 (running the absolute latest Android build pushed out by Google)... so it seems like it shouldn't be a 'cutting edge O/S' issue. I suppose it could be a Samsung TouchWiz issue, but, then again, I don't have any problems running on older TouchWiz devices (S3, S2, etc.)

Additioanlly, I, unfortunately, won't actaully be able to get physical access to an S4 to do any hands on debugging. Does anyone have any tips or 'best practices' of how I might be able to best troubleshoot/collect data from the device short of manually adding a ton of deug prints to a file that my friend can then email me?

FussenKuh

  • Newbie
  • *
  • Thank You
  • -Given: 0
  • -Receive: 0
  • Posts: 6
    • View Profile
Re: Samsung Galaxy S4 Unity + NGUI Issues?
« Reply #1 on: May 23, 2013, 06:08:54 PM »
Looks like I'm using NGUI Pro version 2.3.6.  I'm reluctant to update to the latest version this late in my development cycle, but, might give it a try if no other leads present themselves.

Sent off a couple debug builds to my Galaxy S4 wielding friend to see if I can figure out any other useful info.  Hopefully, he'll get back to me soon.

ArenMook

  • Administrator
  • Hero Member
  • *****
  • Thank You
  • -Given: 337
  • -Receive: 1171
  • Posts: 22,128
  • Toronto, Canada
    • View Profile
Re: Samsung Galaxy S4 Unity + NGUI Issues?
« Reply #2 on: May 23, 2013, 08:50:48 PM »
3.5.7 may not be compatible with S4. Crashes are rarely caused by NGUI. Nonetheless, you should update.

FussenKuh

  • Newbie
  • *
  • Thank You
  • -Given: 0
  • -Receive: 0
  • Posts: 6
    • View Profile
Re: Samsung Galaxy S4 Unity + NGUI Issues?
« Reply #3 on: May 23, 2013, 09:06:45 PM »
Thanks for the reply. I was actually getting ready to post a 2nd update. I just got some debugging reports back from my S4 tester.

While the problem is still baffling me, I've been able to rule out NGUI as well. He's now running a build with 99% of the NGUI stuff removed and he's still consistently crashing as soon as he gets any touchscreen input. It's time for me to start looking deeper into older Unity incompatibility with newer hardware...

Thanks again. And, once again, fantastic library!