I'm trying to run the Google TV emulator on Ubuntu 12.04. The emulator starts, but hangs at a screen with a Google TV logo in the center of it. I connected via adb and the log is looping with the following messages:
I/CameraService( 1038): CameraService started (pid=1038)
I/AudioFlinger( 1038): AudioFlinger's thread 0x9bb5a78 ready to run
I/ServiceManager( 795): Waiting for service SurfaceFlinger...
I/ServiceManager( 795): Waiting for service SurfaceFlinger...
I/ServiceManager( 795): Waiting for service SurfaceFlinger...
I/ServiceManager( 795): Waiting for service SurfaceFlinger...
I/ServiceManager( 795): Waiting for service SurfaceFlinger...
D/AndroidRuntime( 1048):
D/AndroidRuntime( 1048): >>>>>> AndroidRuntime START com.android.internal.os.ZygoteInit <<<<<<
D/AndroidRuntime( 1048): CheckJNI is ON
E/dalvikvm( 1048): Bad heap size parameters (start=5242880, max=33554432, limit=100663296)
W/dalvikvm( 1048): JNI_CreateJavaVM failed
E/AndroidRuntime( 1048): JNI_CreateJavaVM failed
I/ServiceManager( 782): service 'media.audio_flinger' died
I/ServiceManager( 782): service 'media.player' died
I/ServiceManager( 782): service 'media.camera' died
I/ServiceManager( 782): service 'media.audio_policy' died
I/Netd ( 1050): Netd 1.0 starting
I/ ( 1049): ServiceManager: 0x8c6fed8
E/ ( 1049): Failed to switch to AID_MEDIA user, error -1
W/GoogleTVMediaApi( 1049): InitializeGTVMediaLibraries not implemented
W/AVAPIService( 1049): InstantiateAVAPIService not implemented
W/AudioHardwareInterface( 1049): Using stubbed audio hardware. No sound will be produced.
D/AudioHardwareInterface( 1049): setMode(NORMAL)
There is a new version of the emulator coming (extremely soon). In the interim you can check your AVD parameters. Mine are as follows:
hw.lcd.density=213
hw.keyboard.charmap=Emulator
sdcard.size=1G
skin.name=720p
skin.path=add-ons/addon-google_tv_addon-google-12/skins/720p
hw.cpu.arch=x86
abi.type=x86
vm.heapSize=256
hw.ramSize=1024
disk.dataPartition.size=128
image.sysdir.1=add-ons/addon-google_tv_addon-google-12/images/x86/
The error arise because of "Bad heap size parameters ".
So resize the heap size:for me, I change heap size from 64 to 128.
In edit Android Virtual Device.
Related
I have a Flutter app (using version 2.5.1) that
Runs on a simulator
Run on a physical iOS device
Runs when I distribute it using TestFlight
Has integration tests, that run just fine on the simulator.
The app uses Flutterfire and the integration tests uses parts of the app that use Flutterfire.
However, when I follow these instructions in order to create something that can eventually be distributed to Firebase Test Lab, I stumble on the penultimate step:
xcodebuild test-without-building -xctestrun "build/ios_integ/Build/Products/Runner_iphoneos15.0-arm64-armv7.xctestrun" -destination id=<MYDEVICEID>
The app deploys to the physical device, and starts to run, but seems to fail to connect to any Firebase back-ends.
The logs have errors that look like those below.
Any pointers as to how I can fix this will be much appreciated!
Test Suite 'All tests' started at 2021-09-23 18:50:58.044
Test Suite 'RunnerTests.xctest' started at 2021-09-23 18:50:58.045
Test Suite 'RunnerTests' started at 2021-09-23 18:50:58.045
Test Case '-[RunnerTests testIntegrationTest]' started.
2021-09-23 18:50:58.047998+0100 Runner[404:7739] flutter: 00:00 +0: Porridge (setUpAll)
2021-09-23 18:50:58.049466+0100 Runner[404:7739] flutter: 00:00 +1: Porridge Create User
2021-09-23 18:50:58.052143+0100 Runner[404:7734] 8.6.0 - [Firebase/Analytics][I-ACS023007] Analytics v.8.6.0 started
2021-09-23 18:50:58.052457+0100 Runner[404:7734] 8.6.0 - [Firebase/Analytics][I-ACS023008] To disable debug logging set the following
application argument: -noFIRAnalyticsDebugEnabled
2021-09-23 18:50:58.062413+0100 Runner[404:7730] [connection] nw_socket_handle_socket_event [C1.1:2] Socket SO_ERROR [61: Connection r
efused]
2021-09-23 18:50:58.062759+0100 Runner[404:7730] [connection] nw_socket_handle_socket_event [C1.2:2] Socket SO_ERROR [61: Connection r
efused]
2021-09-23 18:50:58.063110+0100 Runner[404:7730] Connection 1: received failure notification
2021-09-23 18:50:58.063199+0100 Runner[404:7730] Connection 1: failed to connect 1:61, reason -1
2021-09-23 18:50:58.063314+0100 Runner[404:7730] Connection 1: encountered error(1:61)
2021-09-23 18:50:58.063936+0100 Runner[404:7730] Task <0B92B415-FE63-4467-8248-8FB5B411688A>.<1> HTTP load failed, 0/0 bytes (error co
de: -1004 [1:61])
2021-09-23 18:50:58.064589+0100 Runner[404:7730] Task <0B92B415-FE63-4467-8248-8FB5B411688A>.<1> finished with error [-1004] Error Dom
ain=NSURLErrorDomain Code=-1004 "Could not connect to the server." UserInfo={_kCFStreamErrorCodeKey=61, NSUnderlyingError=0x281c31890
{Error Domain=kCFErrorDomainCFNetwork Code=-1004 "(null)" UserInfo={_kCFStreamErrorCodeKey=61, _kCFStreamErrorDomainKey=1}}, _NSURLErr
orFailingURLSessionTaskErrorKey=LocalDataTask <0B92B415-FE63-4467-8248-8FB5B411688A>.<1>, _NSURLErrorRelatedURLSessionTaskErrorKey=(
"LocalDataTask <0B92B415-FE63-4467-8248-8FB5B411688A>.<1>"
), NSLocalizedDescription=Could not connect to the server., NSErrorFailingURLStringKey=http://localhost:9099/www.googleapis.com/identi
tytoolkit/v3/relyingparty/signupNewUser?key=AIzaSyCHkqtqAXDFllu7SmuwSw8_pudpAn-dzdM, NSErrorFailingURLKey=http://localhost:9099/www.go
ogleapis.com/identitytoolkit/v3/relyingparty/signupNewUser?key=AIzaSyCHkqtqAXDFllu7SmuwSw8_pudpAn-dzdM, _kCFStreamErrorDomainKey=1}
2021-09-23 18:50:58.065318+0100 Runner[404:7739] flutter: [firebase_auth/network-request-failed] Network error (such as timeout, interrupted connection or unreachable host) has occurred.
2021-09-23 18:50:58.065511+0100 Runner[404:7739] flutter: #0 MethodChannelFirebaseAuth.createUserWithEmailAndPassword (package:firebase_auth_platform_interface/src/method_channel/method_channel_firebase_auth.dart:272)
...etc....
Flutter app is crashing on release mode only .
e service connection to gms implementation 2020-06-27 17:33:50.943
11703-11703/io.appplus.sharechapplus V/FA: Registered activity
lifecycle callback 2020-06-27 17:33:50.947
11703-11703/io.appplus.sharechapplus I/FirebaseInitProvider:
FirebaseApp initialization successful 2020-06-27 17:33:50.976
11703-11723/io.appplus.sharechapplus E/MemoryLeakMonitorManager:
MemoryLeakMonitor.jar is not exist! 2020-06-27 17:33:50.978
11703-11703/io.appplus.sharechapplus E/Minikin: Could not get cmap
table size! 2020-06-27 17:33:50.982
11703-11703/io.appplus.sharechapplus V/ActivityThread: Skipping new
config:{1.0 405mcc862mnc [en_US] ldltr sw360dp w360dp h693dp 320dpi
nrml long port finger -keyb/v/h -nav/h appBounds=Rect(0, 0 - 720,
1440) nonFullScreen=0 suim:1 s.133}, config:{1.0 405mcc862mnc [en_US]
ldltr sw360dp w360dp h693dp 320dpi nrml long port finger -keyb/v/h
-nav/h appBounds=Rect(0, 0 - 720, 1440) nonFullScreen=0 suim:1 s.133} for app:io.appplus.sharechapplus 2020-06-27 17:33:51.002
11703-11703/io.appplus.sharechapplus V/HwPolicyFactory: : success to
get AllImpl object and return.... 2020-06-27 17:33:51.014
11703-11703/io.appplus.sharechapplus V/HwWidgetFactory: : successes to
get AllImpl object and return.... 2020-06-27 17:33:51.020
11703-11703/io.appplus.sharechapplus V/ActivityThread:
callActivityOnCreate 2020-06-27 17:33:51.025
11703-11703/io.appplus.sharechapplus V/FA: onActivityCreated
2020-06-27 17:33:51.071 11703-11703/io.appplus.sharechapplus
E/flutter: [ERROR:flutter/runtime/dart_vm_data.cc(18)] VM snapshot
invalid and could not be inferred from settings. 2020-06-27
17:33:51.072 11703-11703/io.appplus.sharechapplus E/flutter:
[ERROR:flutter/runtime/dart_vm.cc(248)] Could not setup VM data to
bootstrap the VM from. 2020-06-27 17:33:51.072
11703-11703/io.appplus.sharechapplus E/flutter:
[ERROR:flutter/runtime/dart_vm_lifecycle.cc(84)] Could not create Dart
VM instance. 2020-06-27 17:33:51.072
11703-11703/io.appplus.sharechapplus A/flutter:
[FATAL:flutter/shell/common/shell.cc(268)] Check failed: vm. Must be
able to initialize the VM. 2020-06-27 17:33:51.072
11703-11703/io.appplus.sharechapplus A/libc: Fatal signal 6 (SIGABRT),
code -6 in tid 11703 (s.sharechapplus), pid 11703 (s.sharechapplus)
2020-06-27 17:33:51.085 11703-11746/io.appplus.sharechapplus V/FA:
Collection enabled 2020-06-27 17:33:51.086
11703-11746/io.appplus.sharechapplus V/FA: App package, google app id:
io.appplus.sharechapplus,
1:924335965951:android:872d03adb90ca78532eeca 2020-06-27 17:33:51.092
11703-11746/io.appplus.sharechapplus I/FA: App measurement is starting
up, version: 16250 2020-06-27 17:33:51.092
11703-11746/io.appplus.sharechapplus I/FA: To enable debug logging
run: adb shell setprop log.tag.FA VERBOSE 2020-06-27 17:33:51.092
11703-11746/io.appplus.sharechapplus I/FA: To enable faster debug mode
event logging run:
adb shell setprop debug.firebase.analytics.app io.appplus.sharechapplus 2020-06-27 17:33:51.093
11703-11746/io.appplus.sharechapplus D/FA: Debug-level message logging
enabled 2020-06-27 17:33:51.094 11703-11746/io.appplus.sharechapplus
V/FA: Persisting first open: 1593259430937
Flutter (Channel stable, v1.17.4, on Linux, locale en_US.UTF-8)
• Flutter version 1.17.4 at /home/midhilajm/flutter
• Framework revision 1ad9baa8b9 (10 days ago), 2020-06-17 14:41:16 -0700
• Engine revision ee76268252
• Dart version 2.8.4
I am using wildfly-10.1.0.Final.zip, start in domain mode in CentOS 6.6, some how it will shutdown accidently and the error as below:
2017-05-15 21:01:20,103 INFO [org.jboss.as.host.controller] (Thread-2) WFLYHC0181: Host Controller shutdown has been requested via an OS signal
what may cause this error,thank you
These are likely the causes,
Ctrl+c, kill -HUP , kill -INT , kill -TERM , and or System.exit call
I tried to terminate the current JBoss session using Control + c on the command line.
Now when i try to start the server, I get
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:750]
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
Control-C probably didn't terminate the previous process cleanly.
If you're running this on Windows then use the Task Manager to find the old JBoss process and kill it. The process will be listed as java.exe or javaw.exe
If its Linux use ps -ef | grep standalone.sh to find the process id and then kill it.
While I running Jave ME project via Eclipse and Jave_ME_SDK_3 on Mac OS, it prompt an error on the console.I am getting Following Error
Failed to connect to device 1!
Reason:
Emulator 1 terminated while waiting for it to register