I've connected the offical touchscreen display via DSI to my Raspberry Pi 3 running the latest Android Things developer preview.
While booting the android things logo shows up and afterwards the new DP6 settings appear just fine.
When I install an app via adb the screen stays black and no suspicious log message shows up.
In DP 5.1 I had no problems with this.
Also tried running this example:
https://github.com/androidthings/sample-simpleui
Furthermore maxing out the screen brightness with the ScreenManager didn't help.
Any ideas?
Reflashing the image with the Android Things Setup Utility fixed my issue.
Related
i got some problems with the Samsung Smart TV SDK Emulator for VirtualBox.
I have installed the VirtualBox-Version 4.2.16 and when I try to load the 2014_Smart_TV_Emulator_5_1.ova, it always shows after the boot logo , a grey screen. I already used Google to search the problem but could not find anything.
Can some help me or has the same problem to face with the emulator ?
Thanks
Regards
Kami
I tried several apps running in fresh install (yosemite) of Xcode 6.3 simulator but all of them displays only on first 1/4 of simulator screen.
I changed scaling - did not help.
All devices have this problem.
On another mac the apps are displaying in simulator correctly.
Here the screenshot from simulator:
I frequently have this issue with a VMWare OSX development machine I'm using to develop iOS native apps. From what I've seen it is related to the Window > Scale menu option being set to something different than 100% from a previous launch that messes around all the subsequent initialization phases.
To get rid of it, try doing this:
Exit from VMWare full-screen mode, switching to windowed mode instead.
launch iOS Simulator using its stand-alone shortcut (not from XCode) and wait until it finishes loading/booting the default device.
go to Window > Scale and set it to 100%.
go to iOS Simulator > Reset contents and settings... and click OK.
close and reopen the iOS Simulator using its stand-alone app (not from XCode).
As soon as you see it loading without the glitch, you can switch back to VMWare full-screen mode and also use the Window > Scale as you like.
We're developing a web app that extensively uses Cavas 2D for some demos, and is successfully running on both iOS and Android devices. Recently we've added stand-alone mode for iOS devices, so user has to "Add-To-Home-Screen" and run it using screen icon, just like regular app.
What happens recently is that after 10-12 times we start the web app on iPhone4:
Status bar (initially set to 'black') suddenly turns white and we cannot exit Safari (by pressing home button).
If we try to make screen shot (home + power button), shutter sound is played as if screen shot was taken and saved.
If we try to lock the device (power button), screen turns black, but no action after that can bring unlock-screen or any screen for that matter - display remains black.
We can only do reset by pressing home + power for 10 seconds after this point.
If we do not lock the device, web app continuously work with no issues at all, it does not crash, but cannot exit it (double click on home button also has no result).
Has anyone experienced this with their web apps?
Any guidance in how to debug this would be highly appreciated. We've tried using Safari on OSX, connect iPhone to it and use Develop -> iPhone menu but no luck so far.
Thanks in advance!
I would start trying to debug by running XCode with the iPhone connected to the computer.
In XCode open "Organizer" and go to the tab "Devices".
You should see your device there, from which you can view the iOS console. That might be able to tell you what is going wrong with the phone stops responding.
I don't think you have to put the phone in development mode (or be a paid developer) to see the iOS console.
I am on a process of converting an Android app to run in Blackberry platform and to publish it in BlackBerry World (BB Market place).
So I continued to follow the following TUTORIAL and yes it runs well in BlackBerry 10 Device Simulator but with some issues.
In the android App, it has seperate UIs defined for the main screen catogories as follows and works great in all the screen sizes when it is running on android.
layout-small
layout
layout-large
But the converted App to BB, in some cases a part of the UI from the bottom goes beyond the screen limit (In BB 10 device simulator) and does not fit well with the blackberry screen. Basically UI height is too much for BB 10 emulator screen
Also when I check in the converted app while it's running on BB 10 Device simulator it has refered to the UIs defined under layout-small from android APP.
So my questions are
1). What can I do to make the UIs fit well (In converted android App to BB) with all the screen sized BlackBerry devices?
2). How can I ensure that the app will work fine in all the Blackberry screen sizes? (Cause I am using BB 10 device simulator and found no way to get BB Z10 or Q10 device skins)
3). Is it possible to convert the Android app to work fine with pre blackberry 10 OS versioned devices? (As I am not getting the exact point explaining under the "Overview" section of the following LINK)
If someone have experienced the above issues and found solutions would be great to hear and also aprreciate any guidance to get this sortedout. Thanks in advance...!!!
1.) That's a tricky point. If the layout-small is used, I guess you are using the 720x720 simulator, which is Q10 resolution (the Z10 will use layout-large, according to http://supportforums.blackberry.com/t5/Android-Runtime-Development/Android-drawable-folder-layout-folder-for-BB-Z10-and-Q10/m-p/2169275#M3862). Your layout is probably not adapted for a square screen. I'll guess there's no magical answer: you'll have to adapt it. Maybe try it with a Z10 resolution (see point 2) first, to check that it solves your issue.
2.) With the latest simulator, you can choose between a 1280x768 (Z10) or 720x720 (Q10) screen. If the layout is displaying fine on both screen sizes on the emulator, it will display fine on real devices. To change between Z10 and Q10 resolution, you have a number to choose when the emulator is starting (at the very begining).
3.) Android apps runs on two kind of devices: the PlayBook, running BB Tablet OS, and BB10 devices (Q10/Q5/Z10). I guess your question was related to BBOS 7 and before. No, there's no way to run Android apps on them.
One of our clients has come back to us today with a bug that has been found on the Torch 9860 (running OS 7.0).
It seems my app is running in a small box in the centre of the screen, with a big blue border surrounding it. If the soft keyboard is not showing, there is a black box where the keyboard would be.
This issue has not been reported before on other devices, and the app has been "in the wild" for a while. I have not seen it on our test devices - but do not have a Torch 9860 to test with.
I have attached photos of the app running on the device. The blue border is the problem - normally my app would fill the whole screen. I did not create the blue border (to the best of my knowledge).
Apologies for the photos - this is what they sent to us.
Showing the app running in a small box surrounded by the blue border. Note the black space where the keyboard would be if it was required.
Showing the app with the soft keyboard visible.
With some googling, I found 1 possible reference to this issue to do with an instant messaging app not showing correctly on 9860. Feedback was that they were looking into it.
I wonder who else has seen this, or can recommend solutions?
Updates
runs fine on the 9860 emulator
seems to be mentioned in this thread: Blackberry OS 7 Compatibility failed with 9860/9850 device
Thanks, Rafael (left answer in a comment to my question).
Based on the comment I told the client to run the app in compatibility mode (accessed through the system options - application options menu). This seems to have fixed the problem without me having to recompile for SDK 7.0 (also I don't have to start supporting multiple OS's yet).
I already had the blackscreen on bottom when the keyboard should be popped. But it happened rarely and get resolved with an update of the Blackberry
Ask for the OS version/platform of the Blackberry, and propose a update to him, if available.