Build and run problem in samsung galaxy s3

[CodeDK]

Hey
I’ve searched google and the forums, but I can’t seem to find any info on this. I can’t build and run with my samsung galaxy s3 in unity, it worked fine with my HTC phone but the samsung s doesn’t seem to work. I’ve tried the kies drivers but they didn’t do anything for me either.

Anyone else had the same problem?

[StaticNova]

@Code.dk

Hey
I’ve searched google and the forums, but I can’t seem to find any info on this. I can’t build and run with my samsung galaxy s3 in unity, it worked fine with my HTC phone but the samsung s doesn’t seem to work. I’ve tried the kies drivers but they didn’t do anything for me either.

Anyone else had the same problem?

I’m assuming you’re on Windows?

Go to device manager, right click the device and hit update driver software. Manually select driver location and point it too [Android SDK Location]/Extras/Google

Hope this helps.

[CodeDK]

It seems it already used that driver. I tried updating it anyway, but that didn’t work

Some more info: The phone works well with windows and I have no problems getting stuff on the sdcard/internal through the usb cable. Unity just doesn’t want to build and run

It comes as far as to tell me it is pushing content to “somelongweirdname”, which I would assume is because it actually found the phone, but the phone might deny it. This is afterwards:

[Raigex]

Sorry if this is a stupid question and you already did it but did you enable USB debugging?

[miksumortti]

“See the console for details”, does the full editor log say anything more?

[CodeDK]

USB debugging is enabled.
The console doesn’t include any more information than the picture I uploaded…

I’ve read somewhere else that it could be a space problem on the internal drive, but that can’t be the case here since I still have at least 8 gb on the internal and the apk is only 6-7 mb…

[miksumortti]

@Code.dk

The console doesn’t include any more information than the picture I uploaded…

Did you also check the editor log? It usually says much more details about problems. Click the up-right corner button in console to read it.

[CodeDK]

@miksumortti

Did you also check the editor log? It usually says much more details about problems. Click the up-right corner button in console to read it.

Ah thanks, yeah well…
It says:

nloading 0 unused Assets to reduce memory usage. Loaded Objects now: 663. Operation took 7.261105 ms.
System memory in use: 90.7 MB.
Installation failed with the following output:
pkg: /data/local/tmp/Package.apkFailure [INSTALL_FAILED_INVALID_APK]4938 KB/s (7160489 bytes in 1.416s)
UnityEngine.Debug:Internal_Log(Int32, String, Object)
UnityEngine.Debug:LogError(Object)
PostProcessAndroidPlayer:UploadAndStartPlayer(String, String, String, String, String, Boolean, Boolean, Boolean) (at C:\BuildAgent\work\812c4f5049264fad\Editor\Mono\BuildPipeline\PostProcessAndroidPlayer.cs:833)
PostProcessAndroidPlayer:PostProcessInternal(BuildTarget, String, String, String, String, String, String, BuildOptions) (at C:\BuildAgent\work\812c4f5049264fad\Editor\Mono\BuildPipeline\PostProcessAndroidPlayer.cs:492)
PostProcessAndroidPlayer:PostProcess(BuildTarget, String, String, String, String, String, String, BuildOptions) (at C:\BuildAgent\work\812c4f5049264fad\Editor\Mono\BuildPipeline\PostProcessAndroidPlayer.cs:147)
UnityEditor.PostprocessBuildPlayer:Postprocess(BuildTarget, String, String, String, Int32, Int32, String, String, BuildOptions, RuntimeClassRegistry) (at C:\BuildAgent\work\812c4f5049264fad\Editor\Mono\BuildPipeline\PostprocessBuildPlayer.cs:250)
UnityEditor.BuildPipeline:BuildPlayerInternalNoCheck(String[ ], String, BuildTarget, BuildOptions, Boolean)
UnityEditor.BuildPlayerWindow:BuildPlayerWithDefaultSettings(Boolean, BuildOptions, Boolean) (at C:\BuildAgent\work\812c4f5049264fad\Editor\Mono\BuildPlayerWindow.cs:606)
UnityEditor.BuildPlayerWindow:BuildPlayerWithDefaultSettings(Boolean, BuildOptions) (at C:\BuildAgent\work\812c4f5049264fad\Editor\Mono\BuildPlayerWindow.cs:483)
UnityEditor.BuildPlayerWindow:BuildPlayerAndRun() (at C:\BuildAgent\work\812c4f5049264fad\Editor\Mono\BuildPlayerWindow.cs:435)

(Filename: C:/BuildAgent/work/812c4f5049264fad/Editor/Mono/BuildPipeline/PostProcessAndroidPlayer.cs Line: 833)

Error building Player: UnityException: Unable to install APK!
Installation failed. See the Console for details.

(Filename: Line: -1)

• starting compile Library/ScriptAssemblies/Assembly-CSharp.dll, for buildtarget 13
  Unloading 56 Unused Serialized files (Serialized files now loaded: 0 / Dirty serialized files: 0)

Unloading 58 unused Assets to reduce memory usage. Loaded Objects now: 666. Operation took 20.108573 ms.
System memory in use: 90.7 MB.

*** Cancelled ‘Build.Player.AndroidPlayer’ in 56 seconds

A problem with the PostProcessAndroidPlayer maybe?

[miksumortti]

Installation failed with the following output:
pkg: /data/local/tmp/Package.apkFailure [INSTALL_FAILED_INVALID_APK]4938 KB/s (7160489 bytes in 1.416s)

hmm… that looks odd.
Have you tried to only build the apk, and install it with the device to see if it’s just a ‘build run’ problem?

[CodeDK]

@miksumortti

hmm… that looks odd.
Have you tried to only build the apk, and install it with the device to see if it’s just a ‘build run’ problem?

Ye ye, the apk works fine! I’m just annoyed that I have to take these extra steps when build run is so much easier

[miksumortti]

@Code.dk

Ye ye, the apk works fine! I’m just annoyed that I have to take these extra steps when build run is so much easier

Oh ok, I use only build all time
Have you checked some of the results that googling “INSTALL_FAILED_INVALID_APK” gives? Seems like there are some similar problems, though not Unity related I think.

like here: http://youtrack.jetbrains.com/issue/IDEA-86184 . Maybe it’s a problem with the package name? I don’t know, just guessing…

[bitter]

Do you mind checking the device logcat for any errors during the “build run”?

[sonicviz]

I have a Galaxy S3 Alpha on Win 7 X64 Unity 4 pro and no problems with Build and Run (apart from issues with android audio, but that’s different from deploying to test)

Sounds like a problem detecting the needed APK?

[CodeDK]

Here’s the logcat:

@miksumortti - the package name follows conventions, so that’s not the problem

@sonicviz - well as the logcat says it does detect the apk, but it denies it for some reason

[miksumortti]

Do you have the ‘allow unknow sources’ option enabled on your s3?

[CodeDK]

@miksumortti

Do you have the ‘allow unknow sources’ option enabled on your s3?

Yeah it’s on, but it would also have to be if I transfered the .apk, since it hasn’t been signed
But I don’t understand why it doesn’t accept it. There was someone on a forum I checked yesterday (can’t remember where) that stated the reason could be that the installer doesn’t have write rights to the folder. This wasn’t Unity though, but his solution was to symlink the tmp folder to his FAT formatted sdcard; I did try that, but I wasn’t allowed to simlink to my sdcard.

I have rooted my phone, not sure if THAT should have anything to do with this, because it didn’t work before root either.

[miksumortti]

@Code.dk

This wasn’t Unity though, but his solution was to symlink the tmp folder to his FAT formatted sdcard; I did try that, but I wasn’t allowed to simlink to my sdcard.

I have rooted my phone, not sure if THAT should have anything to do with this, because it didn’t work before root either.

Maybe you could use bind mounting instead of symlink. This works for me for example in creating an sd shortcut to my internal storage. I couldn’t also use symlink but this seems to work like it:

$ su
# mount -o bind path-you-want-to-bind path-where-you-want-to-bind

[CodeDK]

@miksumortti

Maybe you could use bind mounting instead of symlink. This works for me for example in creating an sd shortcut to my internal storage. I couldn’t also use symlink but this seems to work like it:

$ su
# mount -o bind path-you-want-to-bind path-where-you-want-to-bind

I just tried it out, but didn’t have any effect.

What I did:
$ su
mount -o /data/local/tmp /storage/sdcard0/tmp

This is really weird. And since I can’t really find other cases of this problem, I guess other galaxy s3s work fine :S

[miksumortti]

@Code.dk

I just tried it out, but didn’t have any effect.

What I did:
$ su
mount -o /data/local/tmp /storage/sdcard0/tmp

Did you write the ‘bind’ after ‘-o’ (or just forgot it qhen typing here…)? And I think that folder (tmp in sdcard) needs to be there before running the command (In case you hadn’t made it)

[CodeDK]

@miksumortti

Did you write the ‘bind’ after ‘-o’ (or just forgot it qhen typing here…)? And I think that folder (tmp in sdcard) needs to be there before running the command (In case you hadn’t made it)

I forgot the bind x) It binds it now and if I place something in /data/local/tmp I can see it in the tmp folder (which I created) on the sdcard.

This doesn’t help on the problem though, I restarted unity and tried build&run again but it failed again T_T