I am trying to develop a samsung smart tv app, which so far works quite well on Samsung SDK's emulator (I am using version 3.5.2), however when I sync my app on a smart tv, the result is not the same as running at emulator.
For example, at scene A, when I press button left, I suppose to navigate to scene B, which works as expected in emulator.
However at the real smart tv, when I press button left, nothing happens, and the log has a strange error message: cannot run current focused scene's key handler.
I have searched the official Samsung development forum but seems not many people face this problem, anyone can help and tell me why I get this error and how can I solve it ?? Thanks!
you need to pass the focus to the new scene that you want to be active.
For example scene2.focus()
Also you should update the SDK, 3.5 is quite old! Try using Samsung SDK 4.5
Related
Has anyone noticed that the Simulator in the Actions on Google Console has been updated and it no longer is an accurate simulation of the assistant app on devices?
They added a display tab but it seems to not show all the output. My application often includes 2 chat bubbles in one response and the new simulator only displays one even though the tts for both is heard in the audio.
I have the same problem. Hope they don't remove the ability to add to responses. It would look terrible with only one line.
Im trying to run the sample app provided in the daydream page on the google pixel phone.
1) I chnaged the build settings to android.
2) Went to player settings enabled Virtual reality support and selected google daydream as the platform.
3) I changed the Minumum API to API level 24.
4) I added the folder containing my adb to the path variable in windows.
5) I also set the path of the android SDk.
6) I enabled USB debuggin on Pixel
However when I run my app , I get the following errors:
Device daydream not supported in Editor Mode. Please run on target device.
And..
Failed to read from controller emulator app event socket.
Verify that the controller emulator app is running.
build the apk and start it on your device. build and play requires adb.
As I suppouse, you want to DEBUG your Daydream app on your Programming Environment (Unity in this case).
Note:This solution allows you to debug on your PC but you'll need one Pixel Phone connected to your PC, and one Daydream Controller.
First of all I recommend you to download the samples provided by Google on Github if you have not done it yet:
https://github.com/googlevr/gvr-unity-sdk/releases
When you load any scene you'll see that the Daydream basic set is composed for a hierarchy like:
The two selected components are key for your porpouse cause if you want to debug Daydream from your PC you'll need to "link" your daydream controller with InstantPreview App. Instant preview will downloaded instantly on your phone if you got in your scene the "GvrInstantPreviewMain".
InstanPreview Google Info: https://developers.google.com/vr/develop/unity/instant-preview
When the app has been opened, can happen 3 things on your pixel phone:
Everything works as it should.
Daydream Instant Preview infom to correct the device by USB.
Kind of Grey screen with some text.
If you're on 2.
This seems to happen when your Unity Project is desynchronized from your phone and you'll see something like:
Close InstantPreviewApplication on your phone, close your unity project (remember to save your progress), and open again your unity project. That has almost always solved me.
If you're on 3.
This seems to happens when instan preview is waiting for Unity Play Mode.
You only need to press Play on you Unity Poject.
Remember to press (and mantain) synchronize button on your Daydream controller if you can move the headset camera but can't find your controller reticle.
This works for me.
I also append my own Unity project with this scheme that works bought for Daydream and GearVR in case helps someone else to test my solution:
https://github.com/ls29322/VR_GalleryApp
I desperately need to use the Safari console on iOS 7 to debug a site. I've hooked my iPhone (5) displaying the site to my Mac. I've started Safari (v6.0.5), gone to the Develop menu, and started the web inspector for the site I'm on. I can see the list of elements on the site, which confirms I'm inside the correct inspector.
From what I've read, the logs to the console should be displayed inside the Logs section, and from what I've found inside Apple's iOS Safari documentation, I should be able to view logs inside there. For me though, nothing is ever logged. I can't even access any variables or functions; when I type anything in (e.g. document.title), it just 'logs' exactly what I've written, with the text I've just typed still in the input field. However, typing something that causes the browser on the device to show life works (e.g. alert('hi'); displays the alert dialog box on the device).
Can anyone help? This issue we have is only happening on iOS, and there's barely any other way to find what's going wrong. Is this problem limited to iOS 7?
I can confirm that this is an iOS 7 issue. The console.log statement works fine when using an iOS 6 or below device, but with iOS 7 won't show at all :(
Apple == new Microsoft();
Only minutes after posting this I got logging to work again, not sure if this is required, but it seemed to do magic for me:
Connect iOS 7 device
Open XCode
Setup device for development
Connect using Safari
Presto, I can see log messages again?!? (Mind you, I had not made any code-changes)
I had the same problem, just after updating to iOS 7. The solution was to update safari to the latest version for developers, which is version 6.1.
i'm new into programming for android. And i have few problems with connecting and debugging my eclipse project on android device - which is my phone Samsung Galaxy SIII. According to this link I tried to launch my app on my phone. Saddly when i press run button it tells me that there's no android device connected. And as you may know im not that dumm to not plug it into my computer. Additionally i have USB Debug mode ticked in options. My PC recognises it as "SAMSUNG Android ADB Device".
Some of you might say that i should start using emulator to have better view how this app will work on other phones/versions of android/etc. Thing is that my PC is quite old, and running an emulator makes it respond so slowly that it's nearly impossible to do anything on this emulated device. Plus... im quite sure that i wont publish this app on play store so i dont need to know if it will work on other devices. I just want to make a weather widget for me since stock one that uses accuweather.com tends to fail weather forecast for my country (like it says heavy rain on sunny day).
So here are the things that i have done so far to try to launch:
1. Uninstalled device and set some new drivers that should have helped me - saddly not ;]
2. Tried launching it via command line
3. I found somewhere on the Internet that it is possible to connect and test your app via WiFi using tcpip over 5555 port... saddly it failed too.
Any ideas what else should i try to make it work?
Solution: Why is Eclipse's Android Device Chooser not showing my Android device?
THis is getting annoying. My device shows up in eclipse on all
platforms.. Except when I am on my Ubuntu laptop.. when I "run
configurations" with it set to Manual.. I can see that there is an
Emmulator running that I can Install the App to.
Problem is, the Emulator is a pile of horse crap when it comes to
testing on real devices like my Samsung Captivate.
When the Captivate is plugged in via USB.. it shows via ICON, except
the ID is set to ??????????? and nothing else seems to be registering.
I can highlight it, but I can't launch it.
The captivate I am using is Rooted and running the LagFix Kernal..
However this has never hindered me on Windows or OSX.
Help.. I am trying to go completely Linux.. if it kills me.
See screenshot below: http://img265.imageshack.us/i/sdkbugeclipse.png/
UPDATE: Device is showing in the manager even when not connected?!?!
This has to be some weird Eclipse bug.. PLEASE HELP!
Solution (in case you missed my edit) need to add the correct Samsung Device ID when using the SDK with Ubuntu: link